[Pkg-sysvinit-devel] Bug#510455: initscripts: fails to boot when debug=echo uncommented in /etc/init.d/rc
Arthur Marsh
arthur.marsh at internode.on.net
Sat Jan 3 09:55:50 UTC 2009
Kel Modderman wrote, on 2009-01-03 20:13:
> On Friday 02 January 2009 10:15:51 Arthur Marsh wrote:
>> Package: initscripts
>> Version: 2.86.ds1-61
>> Severity: normal
>>
>>
>> I tried uncommenting the line in /etc/init.d/rc that has
>>
>> debug=echo
>>
>> but after doing so, I not only had problems shutting down but also with
>> restarting, leaving the root filesystem mounted read-only though mount
>> claimed it was read-write.
>
> debug=echo means each command that the script would do is echo'd and not
> actually performed. It is used for development/debugging of script to make
> sure it does things in correct sequence.
>
> I'm not sure this is a bug, but maybe the code comments could be a little more
> verbose than they are currently, and warn people not to leave 'debug=echo'
> uncommented for actual script use.
>
> Thanks, Kel.
>
Thanks, is there any way to run the start-up and shut-down scripts with
the kind of verbosity provided by "sh -x"?
Another wish-list item would be to run the start-up and shut-down
scripts with just enough extra output to indicate what script was being run.
This was all inspired by a problem with SCSI module eata being loaded
due to its inclusion in /etc/modules, but the appearance of the device
files /dev/sda? happening *after* fsck was run on the non-root file systems.
Regards,
Arthur.
More information about the Pkg-sysvinit-devel
mailing list