comp.lang.idl-pvwave archive: archive » Re: spawn issue

Home » Public Forums » archive » Re: spawn issue - was: open sockets

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: spawn issue - was: open sockets [message #53109 is a reply to message #53103]

Tue, 20 March 2007 13:36

Foldy Lajos
Messages: 268
Registered: October 2001

Senior Member

On Tue, 20 Mar 2007, Bringfried Stecklum wrote:

> It is clear now that the issue is unrelated to socket but in fact caused
> by multiple calls to spawn each of which opens a pipe to transfer the
> data like
>
> spawn,'ds9 stdin',unit=unit
> writefits,'/dev/null',image,header,unit=unit
>
> The problem is that after closing ds9 the pipe is still open. It seems
> there is no way to make IDL aware that the child process no longer exists.
>

If you use the exit button in ds9, the pipe will remain open. You should
call 'FREE_LUN, unit' to exit ds9 (and close the pipe).

If you have multiple ds9 windows, you can add titles to them, and record
the title-unit pairs, and write a little procedure to find the unit number
belonging to the title, and call FREE_LUN for it.

regards,
lajos

Report message to a moderator

[Message index]

		Re: spawn issue - was: open sockets By: JD Smith on Wed, 21 March 2007 10:35
		Re: spawn issue - was: open sockets By: Bringfried Stecklum on Wed, 21 March 2007 10:13
		Re: spawn issue - was: open sockets By: JD Smith on Wed, 21 March 2007 09:20
		Re: spawn issue - was: open sockets By: Bringfried Stecklum on Wed, 21 March 2007 06:39
		Re: spawn issue - was: open sockets By: Foldy Lajos on Tue, 20 March 2007 13:36

Previous Topic:	Re: Modis Georeferencing
Next Topic:	Re: Big arrays, reducing data

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 01:38:41 PDT 2025

Total time taken to generate the page: 0.00278 seconds