Bug 443430 - LSB INIT INFO confuses chkconfig
LSB INIT INFO confuses chkconfig
Product: Fedora
Classification: Fedora
Component: chkconfig (Show other bugs)
All Linux
low Severity high
: ---
: ---
Assigned To: Bill Nottingham
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-04-21 10:55 EDT by James
Modified: 2014-03-16 23:14 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-21 13:58:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Current filenames in /etc/rc.d/rc5.d (813 bytes, text/plain)
2008-04-21 13:37 EDT, James
no flags Details
List of installed packages, output from rpm -qa (26.97 KB, text/plain)
2008-04-21 13:38 EDT, James
no flags Details

  None (edit)
Description James 2008-04-21 10:55:03 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
# 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


# 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):
Actual results:
Messed up startup order. If messagebus isn't started early, the result is a mess.

Expected results:
chkconfig gets is priorities in order.
Comment 1 Bill Nottingham 2008-04-21 11:47:31 EDT
What else do you have installed that provides $syslog or $local_fs?
Comment 2 James 2008-04-21 13:37:14 EDT
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.
Comment 3 James 2008-04-21 13:37:48 EDT
Created attachment 303181 [details]
Current filenames in /etc/rc.d/rc5.d
Comment 4 James 2008-04-21 13:38:26 EDT
Created attachment 303182 [details]
List of installed packages, output from rpm -qa
Comment 5 Bill Nottingham 2008-04-21 13:58:45 EDT
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.
Comment 6 James 2008-04-21 14:14:14 EDT
Ahh, I see. I updated to rsyslog-3.14.1-2.fc9 and all seems well now.

Many thanks!

Note You need to log in before you can comment on or make changes to this bug.