Bug 443430

Summary: LSB INIT INFO confuses chkconfig
Product: [Fedora] Fedora Reporter: James <james>
Component: chkconfigAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 8CC: herrold, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-21 17:58:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Current filenames in /etc/rc.d/rc5.d
none
List of installed packages, output from rpm -qa none

Description James 2008-04-21 14:55:03 UTC 
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

#!/bin/sh
#
# 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

Running

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

Many thanks!