Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!uwvax!heurikon!vme.heurikon.com!dougg
From: dougg@vme.heurikon.com (Doug Gillett)
Newsgroups: comp.unix.questions
Subject: Re: Regular FSCK Required ?
Keywords: fsck cron
Message-ID: <166@heurikon.heurikon.com>
Date: 9 Mar 91 01:57:31 GMT
References: <1235@cnw01.storesys.coles.oz.au> <1991Mar8.040254.16272@tvcent.uucp>
Sender: news@heurikon.heurikon.com
Reply-To: dougg@vme.heurikon.com (Doug Gillett)
Organization: Heurikon Corporation, Madison, WI
Lines: 11

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 :-))

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.

Doug