Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uwm.edu!spool.mu.edu!think.com!mintaka!snorkelwacker.mit.edu!thunder.mcrcim.mcgill.edu!mouse
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: comp.unix.questions
Subject: Re: Regular FSCK Required ?
Keywords: fsck cron
Message-ID: <1991Mar15.095247.13441@thunder.mcrcim.mcgill.edu>
Date: 15 Mar 91 09:52:47 GMT
References: <1235@cnw01.storesys.coles.oz.au> <1991Mar8.040254.16272@tvcent.uucp> <166@heurikon.heurikon.com>
Organization: McGill Research Centre for Intelligent Machines
Lines: 25

In article <166@heurikon.heurikon.com>, dougg@vme.heurikon.com (Doug Gillett) writes:
> In article <1991Mar8.040254.16272@tvcent.uucp> andrew@tvcent.uucp (Andrew Cowie) writes:
>> Hey, you could even solve this problem (maybe) by having cron kill
>> off the fscks an hour later if they still exist.  (Emphasis on the
>> maybe; you won't find me trying that on MY system :-))

I have a program called timeout that runs something else, and if it
still hasn't died after some time later (the time being specified in
seconds on timeout's command line), it kills it off.  (Details
available by mail.)

> Another possibility is to use "fsck -n", if available on your system,
> and redirect the output to a file, usually /usr/adm/messages.  The -n
> option answers "no" to any questions fsck might ask.

Unfortunately this is not always what you want.  I would *really* like
an option to fsck that automatically answers "yes" to "CONTINUE?"
messages and "no" to all others.  I suppose I could hack something
together with expect, but it seems to me it belongs in fsck.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu