Red Hat Bugzilla – Bug 443430
LSB INIT INFO confuses chkconfig
Last modified: 2014-03-16 23:14:13 EDT
Description of problem:
LSB INIT INFO causes chkconfig to mess up startup priorities. For example,
dbus-1.1.2-9.fc8's /etc/init.d entry has header
# messagebus: The D-BUS systemwide message bus
# chkconfig: 345 22 85
# description: This is a daemon which broadcasts notifications of system events \
# and other messages. See http://www.freedesktop.org/software/dbus/
# processname: dbus-daemon
# pidfile: /var/run/messagebus.pid
### BEGIN INIT INFO
# Provides: messagebus
# Required-Start: $syslog $local_fs
# Required-Stop: $syslog $local_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: The D-Bus systemwide message bus
# Description: This is a daemon which broadcasts notifications of system
# events and other messages. See http://www.freedesktop.org/software/dbus
### END INIT INFO
# chkconfig --level 3 messagebus resetpriorities
results in S22messagebus getting renamed to S99messagebus.
Remove the LSB block and it behaves properly.
Version-Release number of selected component (if applicable):
Messed up startup order. If messagebus isn't started early, the result is a mess.
chkconfig gets is priorities in order.
What else do you have installed that provides $syslog or $local_fs?
Nothing as far as I am aware. (How would I find out?) The only thing slightly
out of the ordinary is some nss and NetworkManager stuff from development. I'll
attach a list of installed packages.
Created attachment 303181 [details]
Current filenames in /etc/rc.d/rc5.d
Created attachment 303182 [details]
List of installed packages, output from rpm -qa
messagebus requires $syslog.
rsyslog provides $syslog.
Ergo, messagebus is starting after/equal to rsyslog.
(I suspect you've got an issue with rsyslog requiring network, and
NetworkManager providing network, as well.)
See bug 440968 - I suspect if you adjust that in your rsyslog script, things
will behave differently/better. But chkconfig is just trying to honor the deps
as best as possible.
Ahh, I see. I updated to rsyslog-3.14.1-2.fc9 and all seems well now.