make x + mv x z + rm z = crash
amos at instable.UUCP
amos at instable.UUCP
Thu Feb 5 00:49:18 AEST 1987
If you want help from this group please *always* state the type of
system you're on, and preferably the entire hardware configurattion.
Now, down to business: the 'D' status is DELAYED, which means usually
the process is waiting for a device at a high priority; this should
last for only a fraction of a second.
The symptoms indicate either:
- A known problem in BSD4.2's 'close' routine, that crashed the system
if process tries to remove a file while another one is creating it. This
also appeared in Ultrix 1.1; as far as I know it has been fixed in BSD4.3.
- The Fujitsu Eagle disk drive has been known to put itself off-line
spontanously when used with a certain type of controller. This would
leave processes hanging waiting for interrupt.
- Some types of terminal multiplexing devices also tend to hang.
There are a few other possibilities, but since I know nothing about your
sw/hw configuration, I can't give a better answer.
BTW: Anyone out there wishes to contribute horror stories about
the behaviour of Real Systems? :-)
--
Amos Shapir
National Semiconductor (Israel)
6 Maskit st. P.O.B. 3007, Herzlia 46104, Israel
(011-972) 52-522261 amos%nsta at nsc.com 34.48'E 32.10'N
More information about the Comp.unix.wizards
mailing list