Subject: Re: ^C in fsck (segue from tech-kern)
To: Alan Barrett <firstname.lastname@example.org>
From: None <email@example.com>
Date: 04/04/2007 23:31:30
On Wed, Apr 04, 2007 at 10:37:10PM +0200, Alan Barrett wrote:
> On Wed, 04 Apr 2007, der Mouse wrote:
> > Okay, so it's supposed to work in 3.1; I'll work on figuring out why it
> > doesn't. Offhand, it looks as though stop_boot just kills the shell
> > running the fsck script, not the shell running /etc/rc - I suspect it
> > might work if I set rc_fast_and_loose.
> That sounds plausible. Perhaps this patch to /etc/rc would help:
I may not understand correctly the framework, but not stopping on error
for a script in rc.d/ not ending in ".sh" is a feature. To "fault", a
script must end in ".sh".
Since---I was responsible for a thread about the rc.d/ handling last
week---every kind of scripts, now, end in rc.d/, that is not only system
provided (and tested) scripts are here but third parties and perhaps
suboptimal, aborting on any error would be a bad idea, since user level
daemons are not critical and may be more easily fixed in not single user
mode (remote connexion for example).
Thierry Laronde (Alceste) <tlaronde +AT+ polynum +dot+ com>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C