Date: Fri, 14 Apr 1995 09:04:47 -0400 (EDT) From: Network Coordinator <nc@ain.charm.net> To: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>, freebsd-questions@FreeBSD.org Subject: Re: Processes not dying! Message-ID: <Pine.BSF.3.91.950414090033.14236A-100000@ain.charm.net> In-Reply-To: <10499.797848058@freefall.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Apr 1995, Jordan K. Hubbard wrote: > Are they in `D' wait? (see ps). If so, they're blocking on some sort of > I/O that isn't completing. Perhaps a bogus NFS mount, or a device that's > causing problems. > Yes, they were in a D wait. The bogus mount was most likely wuarchive.wustl.edu because at about 5 pm the last couple of days their system has been too busy to deal with NFS packets correctly. The phone company dropped carrier on the line that was using slattach and I checked up on the system a few hours later and EVERYTHING that was not dying was gone. Either it was when wuarchive started accepting packets again or the slip line dying. When I tried to umount wuarchive before that, it said device is busy. -> Is there anyway to hard core, override something like that? If I was running NFSiod I suppose I could have killed it, but I wasn't at the time. Any other suggestions? Thanks for the insight, its really appreciated -- I can't even call the inconveniences (few) that I have had with FreeBSD even real problems, after it was installed its been nothing but the fastest, safest and most stable multi-tasking OS I have used (on any platform). Thanks, -Jerry.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.950414090033.14236A-100000>