I get a failure without any other messages on shutdown or reboot from this system. My boot.log contains no data so I am not sure where else to look for information. The configuration is as installed from a fresh install
kernelopps still failing with latest updates.
I decided to look at some debugging. So I decided to run the init script and do a reload. The unload and reload seem to work. I wonder if the problem is this scripts place in the list. Should this be transfered to the init scripts group ?
Looks like kerneloops has already died by the time the initscript tries to kill it.
Any way that I can help confirm this. On the other hand it does sound like you are already able to make this happen for you?
K73messagebus is killing it. Looks like it needs to require $syslog during shutdown...
so do we need to make it like 72 instead of 90. I could try this and see i anything breaks if this would help.
Should be fixed in 0.10-6
Hi, I still get this problem using kerneloops-0.10-11.fc9.x86_64. I did a yum install kerneloops, then enabled and started the service using system-config-services. In rc6.d/ I have: lrwxrwxrwx 1 root root 20 2008-05-25 08:18 K74kerneloops -> ../init.d/kerneloops lrwxrwxrwx 1 root root 20 2007-03-25 07:41 K74lm_sensors -> ../init.d/lm_sensors lrwxrwxrwx 1 root root 14 2008-05-13 15:56 K74nscd -> ../init.d/nscd lrwxrwxrwx 1 root root 17 2008-05-13 16:14 K74rsyslog -> ../init.d/rsyslog I don't know why it isn't working. Can you maybe try making the kill number lower or something?
It should be 73 after the update: K73auditd -> ../init.d/auditd K73kerneloops -> ../init.d/kerneloops K73messagebus -> ../init.d/messagebus K73winbind -> ../init.d/winbind K73ypbind -> ../init.d/ypbind
I believe that this one is fixed. Shouldn't we close it?
Seems to be working for me now now, thanks.