Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!muffin!libes
From: libes@cme.nist.gov (Don Libes)
Newsgroups: comp.unix.questions
Subject: Re: Regular FSCK Required ?
Keywords: fsck cron
Message-ID: <826@muffin.cme.nist.gov>
Date: 28 Mar 91 03:08:16 GMT
References: <1991Mar15.095247.13441@thunder.mcrcim.mcgill.edu> <11004@dog.ee.lbl.gov> <126605@uunet.UU.NET>
Organization: National Institute of Standards and Technology
Lines: 25

In article <126605@uunet.UU.NET> rbj@uunet.UU.NET (Root Boy Jim) writes:
>In article <11004@dog.ee.lbl.gov> torek@elf.ee.lbl.gov (Chris Torek) writes:
>?In article <1991Mar15.095247.13441@thunder.mcrcim.mcgill.edu>
>?mouse@thunder.mcrcim.mcgill.edu (der Mouse) writes:
>?>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.

For sites that don't have Karel's fix, here's an expect script to do it.

	spawn fsck
	for {} 1 {} {
		expect	"*CONTINUE?*"	{send "y\r"} \
			"*?*"		{send "n\r"} \
			eof		{exit}
	}


>Cannot read superblock: CONTINUE?

I would've liked it better if the message read:

Cannot continue: CONTINUE?

Don Libes          libes@cme.nist.gov      ...!uunet!cme-durer!libes