Date: Sun, 5 Nov 2000 14:49:09 -0800 From: "Crist J . Clark" <cjclark@reflexnet.net> To: David Goddard <goddard@acm.org> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Remotely recovering from a crash Message-ID: <20001105144909.A75251@149.211.6.64.reflexcom.com> In-Reply-To: <3.0.3.32.20001105223907.00803150@dmg.parse.net>; from goddard@acm.org on Sun, Nov 05, 2000 at 10:39:07PM %2B0000 References: <3.0.3.32.20001105223907.00803150@dmg.parse.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 05, 2000 at 10:39:07PM +0000, David Goddard wrote: > Hi, > > 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. ;) > 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? -- Crist J. Clark cjclark@alum.mit.edu 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?20001105144909.A75251>