Date: Sun, 05 Nov 2000 23:43:09 +0000 From: David Goddard <goddard@acm.org> To: cjclark@alum.mit.edu Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Remotely recovering from a crash Message-ID: <3.0.3.32.20001105234309.00814c50@dmg.parse.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.3.32.20001105234309.00814c50>