Date: Wed, 27 Oct 1999 20:25:06 -0500 (CDT) From: Kevin Day <toasty@dragondata.com> To: doconnor@gsoft.com.au (Daniel O'Connor) Cc: remy@synx.com (Remy Nonnenmacher), hackers@FreeBSD.ORG Subject: Re: Running unattended (ifo FFS thread) Message-ID: <199910280125.UAA81599@celery.dragondata.com> In-Reply-To: <XFMail.991028105151.doconnor@gsoft.com.au> from "Daniel O'Connor" at Oct 28, 1999 10:51:51 AM
next in thread | previous in thread | raw e-mail | index | archive | help
> > > On 27-Oct-99 Remy Nonnenmacher wrote: > > In followup of the FFS thread, I would like to know if there are some > > recommendations for running unattended machines. For exemple, avoiding > > the 'run fsck manually' (for exemple, when co-locating a machine far > > away where it is not possible to get a console login). > > Well.. (and I know lots of people would say this is stupid) If you are going to > run it in isolation, then you can change the inital fsck so that it just > assumes yes for all user input in an error condition.. > > This means that it generally always gets through the fsck.. Of course if fsck > had to delete files then they're gone, but if you value its ability to stay up > without human intervention its handy. > The problem is that 'fsck -py' ignores the 'p' and will fsck every time, even if it's unneeded. This takes ages for me. I believe I submitted a PR with a 'fix' to fsck. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910280125.UAA81599>