Date: Thu, 28 Oct 1999 10:51:51 +0930 (CST) From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Remy Nonnenmacher <remy@synx.com> Cc: hackers@freebsd.org Subject: RE: Running unattended (ifo FFS thread) Message-ID: <XFMail.991028105151.doconnor@gsoft.com.au> In-Reply-To: <199910271739.TAA74470@gw0.boostworks.com>
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. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum 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?XFMail.991028105151.doconnor>