On Thu, 28 Oct 1999, Daniel O'Connor wrote:
>
> 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..
we do
fsck -p || fsck -y
>
> 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 [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
