https://bugzilla.novell.com/show_bug.cgi?id=679671 https://bugzilla.novell.com/show_bug.cgi?id=679671#c7 --- Comment #7 from Markus Abt <abt@comet.de> 2011-04-17 18:52:24 UTC --- (In reply to comment #4)
* (for some reason) blogd receives SIGSYS
The signal is intentionally sent by the /etc/init.d/rc script: <snip> # # Do never call startpar for single, halt or reboot script # case "$RUNLEVEL" in S|0|1|6) DO_CONFIRM=no RUN_PARALLEL=no killproc -SYS /sbin/blogd esac </snip> After that, rc starts the scripts for entering the new run level, e.g. /etc/init.d/rc0.d/halt in case of a shutdown. (Note that, at the top of the halt script, RUN_PARALLEL is re-read from /etc/sysconfig/boot and therefore possibly reset to RUN_PARALLEL=yes.) The SIGSYS informs blogd that it should stop writing to disk. However, I have noticed that blogd continues to write to /var/log/boot.(o)msg for some (short) time. Typically, the last message in my /var/log/boot.omsg is "Running /etc/init.d/halt.local done". In the case that some shutdown scripts like unmounting the disks are skipped, I can see some further messages in /var/log/boot.omsg which come from startpar. It looks like this is happening in that particular case: * rc sends SIGSYS to blogd * rc calls halt * halt calls halt.local and does some other stuff * halt calls startpar * startpar calls some of the rc0.d/K* scripts * blogd receives/handles SIGSYS and stops writing to disk * my assumption is: at this point startpar exits with 141, leaving some of the rc0.d/K* scripts uncalled. The best solution for me is to set RUN_PARALLEL=no *in the halt script*. I cannot notice any negative effect on the speed for shutting down. Booting the system still uses RUN_PARALLEL=yes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.