[daip] Lock up with WHICH

[Craig Walker]

I tried to run the AIPS utility WHICH on PARANG on my ULTRA 1.  After
the first couple of hits, it stopped and the windowing system locked
up.  Eventually (>15 minutes later), I went to isleta and logged into
pingora, which worked, although slowly.  I ran top and found that an
xterm was getting nearly 100% of the CPU.  I killed the xterm (kill
three times did not work, so I used kill -9).  That cleared up the
problems in pingora.  I then exited from pingora, but found that I could
not lock the windows on isleta and could not exit the windowing system.
Eventually the KDE bar at th bottom of the screen went away.  I left 
the machine in that state - I have no idea what was going on.

I suspect that the problem on pingora was some combination of a problem
with WHICH, perhaps in trying to access something on the network, and
the problem that I am still having with cpu bound jobs locking up the
windowing system (real annoying).  By the way, I had successfully run
WHICH on PCAL moments before the disasterous run above and it ran fine.

I think I'm back in business now, but thought I should pass on this
experience.

Craig