[Pkg-sysvinit-devel] Bug#595431: Aborting fsck aborts all scripts in rcS.d

[Goswin von Brederlow]

Kel Modderman <kel at otaku42.de> writes:

> On Saturday 04 September 2010 06:39:49 Goswin von Brederlow wrote:
>> Package: insserv
>> Version: 1.14.0-2
>> Severity: critical
>> 
>> Hi,
>> 
>> during boot /etc/rcS.d/S13checkfs.sh starts a filesystem check (hasn't
>> been checked for 197 days) as well as giving some errors for missing
>> devices. Since I didn't want to wait for the fsck before fixing the
>> missing devices I aborted the check with crlt-c. This resulted in the
>> fsck to be aborted but then also skipped all further rcS.d scripts
>> saying:
>> 
>> Running scripts in rcS.d/ took 41 seconds.
>> INIT: Entering runlevel: 2
>> 
>> Given that filesystem weren't mounted or anything that didn't work out
>> well leaving the system unusable.
>> 
>> This is a serious regressions from before insserv. The old behaviour
>> was to display a message asking for the root password to get a shell
>> or ctrl-D to continue booting.
>
>
> How does changing /etc/init.d/rc with the below patch modify behaviour?
>
> Thanks, Kel.
>
> --- rc~
> +++ rc
> @@ -43,7 +43,7 @@ on_exit() {
>  trap on_exit EXIT # Enable emergency handler
>  
>  # Ignore CTRL-C only in this shell, so we can interrupt subprocesses.
> -trap ":" INT QUIT TSTP
> +trap "" INT QUIT TSTP
>  
>  # Set onlcr to avoid staircase effect.
>  stty onlcr 0>&1

Well, ask me in another 197 days when then fsck runs again. :)

Since it doesn't boot without handholding due to mdadm bugs I don't plan
to reboot the system any time soon, with or without forced fsck.

But you can check ourself by forcing a fsck for the next boot.

MfG
        Goswin