[daip] Re: undying TVs

Patrick P. Murphy pmurphy at NRAO.EDU
Tue Dec 19 16:41:35 EST 2000


On Tue, 19 Dec 2000 16:23:13 -0500, Lawrence Rudnick <larry at astro.umn.edu>
   said to "daips": 

> we're running the 31Dec99 (close to the frozen version but not quite I
> think) on several linux machines, but on one of them, the /tmp files do
> not get cleaned out when you "exit" or when you "kleenex" from aips.
> often the LOK files and the T.. files stay around, but the XAS files
> usually go away, so it tries to start up a tv using that slot (with
> tv=local:0) but then refuses to do anything with the tv when it finds
> the LOK file.

I've done a few experiments on my home system (I left early; weather) and
have found a circumstance where garbage is left in the /tmp (or $TMPDIR)
area.  I was able to leave a hanging LOK socket when I started AIPS up
with tv=local but it failed to fire up XAS (I needed to override my
default setting of AIPStv*useSharedMemory), and then kleenex was unable to
shut down that socket because there was nothing on the other end.

When I zapped the orphaned LOK file in /tmp, overrode my resource setting
via xrdb -merge, cleanly shut down the orphaned TVSRV1 process, and fired
up AIPS tv=local again, this time on shutdown it was able to clean up
everything.  It does take about 10 seconds for the tek and message servers
to close down completely; the delay there was deliberate, so a human has
time to read any error message in the xterm before it goes *poof*!.

It may be that a forced unlink() of the socket is appropriate if the
socket shutdown code itself fails, but I'm not sure this would be right in
all circumstances.

I'm not sure this helps much, but it may cast more information on the
problem.
				- Pat



More information about the Daip mailing list