From owner-freebsd-questions Sun Nov 5 15:41:49 2000 Delivered-To: freebsd-questions@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id A73AC37B4D7 for ; Sun, 5 Nov 2000 15:41:45 -0800 (PST) Received: from shootthemlater.demon.co.uk ([194.222.93.84] helo=cerebus.parse.net) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 13sZQ0-0002DQ-0X; Sun, 5 Nov 2000 23:41:44 +0000 Received: from elf.putney.parse.net ([10.0.0.10] helo=elf) by cerebus.parse.net with smtp (Exim 3.16 #1) id 13sZPx-0005pJ-00; Sun, 05 Nov 2000 23:41:41 +0000 Message-Id: <3.0.3.32.20001105234309.00814c50@dmg.parse.net> X-Sender: dmg@dmg.parse.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 05 Nov 2000 23:43:09 +0000 To: cjclark@alum.mit.edu From: David Goddard Subject: Re: Remotely recovering from a crash Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <20001105144909.A75251@149.211.6.64.reflexcom.com> References: <3.0.3.32.20001105223907.00803150@dmg.parse.net> <3.0.3.32.20001105223907.00803150@dmg.parse.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 14:49 05/11/00 -0800, Crist J . Clark wrote: ... >> I'm about to place a FreeBSD box in colocation and I'm trying to do >> everything I can to minimise the need to physically visit the box in order >> to get it up again after a crash (I've had more than one situation where it >> spontaneously rebooted, at least one of which was of the typing dumb >> commands as root variety). > >Then don't do that. ;) Excellent advice, thanks :-) >> The problem I am getting is that after an unclean shutdown, it always >> complains that the /tmp filesystem is unclean and I have to run fsck -p >> from the console. It is only the /tmp fs that this happens to, I presume >> because that was the only one being actively used when the box went down. > >It might also be the way it is entered in /etc/fstab. What's the pass >number? Hmmm... it would appear that the problem exists between keyboard and chair - the dump and pass fields were missing for /tmp. Many thanks for prompting me to actually look at fstab. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message