From owner-freebsd-hackers Sun Apr 7 19:05:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA19175 for hackers-outgoing; Sun, 7 Apr 1996 19:05:06 -0700 (PDT) Received: from zap.io.org (root@zap.io.org [198.133.36.81]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA19168 for ; Sun, 7 Apr 1996 19:05:02 -0700 (PDT) Received: from localhost (taob@localhost) by zap.io.org (8.6.12/8.6.12) with SMTP id WAA17868; Sun, 7 Apr 1996 22:04:47 -0400 X-Authentication-Warning: zap.io.org: taob owned process doing -bs Date: Sun, 7 Apr 1996 22:04:47 -0400 (EDT) From: Brian Tao To: Joerg Wunsch cc: FreeBSD hackers Subject: Re: 'ps' or procfs stuck in disk wait??? In-Reply-To: <199604080123.DAA01911@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Apr 1996, J Wunsch wrote: > > It normally goes back to single-user, or reboots cleanly, even despite > of this message. Your hang must have been somewhere deeper. Even dropping into single-user would not be acceptable in the case of an unmanned POP. When I type "reboot" from a remote session, I expect the machine to bring itself back up again within a couple of minutes, barring hardware failure (which wasn't the case here). -- Brian Tao (BT300, taob@io.org) System and Network Administrator, Internex Online Inc. "Though this be madness, yet there is method in't"