iraf.net

>From sjm@mso.anu.edu.au Mon Jan 27 18:45:26 1997
From: sjm@mso.anu.edu.au (Stephen Meatheringham)
To: fitz@noao.edu
Subject: Re: problem with ximtool + private pipes> To do this properly you would need to set the ximtool 'input_fifo'
> and 'output_fifo' as
>
> Ximtool*input_fifo: /home/sjm/iraf/dev/imt1i
> Ximtool*output_fifo: /home/sjm/iraf/dev/imt1o> I should also mention that w/ Ximtool and 2.10.4 you don't need
> private pipes, the default connection will be on a unique domain socket so
> this is only an issue for SAOimage. Instead of a private graphcap you could
> also force the connection to use the private pipes by defining
>
> setenv IMTDEV fifo:/home/sjm/iraf/dev/imt1i:/home/sjm/iraf/dev/imt1o
>
> Let us know if you continue to have problems.Mike,
I cannot get this to work. If I use the ximtool resources above and/or
the env var I get the same error: ERROR: Cannot open device
(node!imtool,,512,512) However, starting ximtool up using : ximtool -xrm
"*input_fifo:/home/sjm/iraf/dev/imt1i" -xrm
"*output_fifo:/home/sjm/iraf/dev/imt1o" works fine, with or without the
IMTDEV definition. BTW I had definitely made sure the entries had been
picked up from my .Xdefaults file.I'm happy to leave it at that.
Cheers Stephen>From fitz Mon Jan 27 18:51:32 1997
To: sjm@mso.anu.edu.au
Subject: Re: problem with ximtool + private pipesHi Stephen,
Ooops, there was a typo in my resource lines, it should read 'XImtool'
not 'Ximtool'. As for the -xrm settings working: you're resetting the
fifos that way but IRAF isn't using them since it'll connect on the unix
domain socket instead. W/ the IMTDEV def it's using the private pipes defined
by -xrm.Cheers,
-Mike