Some random behaviour

Sergei Naumov wrote on Feb 03, 1998

Hi!
I am running Iraf 2.11 on Solaris 2.5.1. Once in a while I get this error
message that the task "can't connect to a binary blah-blah". It usually
happens when I load astutil with something else (most frequently, digiphot
but sometimes ared also). I have to restart cl to get rid of this.

Anyone knows what to do to fix it?

	Sergei

---

Mike Fitzpatrick wrote on Feb 03, 1998

> I am running Iraf 2.11 on Solaris 2.5.1. Once in a while I get this error
> message that the task "can't connect to a binary blah-blah". It usually
> happens when I load astutil with something else (most frequently, digiphot
> but sometimes ared also). I have to restart cl to get rid of this.

	Is the message "cannot open connected subprocess"?  If so then it
usually means the binaries were installed in the wrong place, e.g. the
NOAO package binaries were installed in the same directory as the core
system binaries.  If this is the case then you should get the message for
all NOAO tasks, and all the time.  Or are you saying that this error just
happens occassionally?  In that case I haven't got a quick answer, it could
be that you've defined something in your login.cl or loginuser.cl that is
causing this in which case try doing a fresh mkiraf from a scratch directory
to see if it happens there as well.
	If you still have problems please send me more information (the
exact error message, and a way to reproduce it if possible).

-Mike

---

Last post on Feb 03, 1998