Red Hat Bugzilla – Bug 161470
Duplicate "Starting postgresql" at boot
Last modified: 2013-07-02 23:06:08 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
When lm_sensors is enabled ('chkconfig lm_sensors on'), "Starting lm_sensors:"
is printed twice when the system boots:
Starting lm_sensors: Starting lm_sensors: [ OK ]
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run /usr/sbin/sensors-detect to configure lm_sensors.
2. '/sbin/chkconfig lm_sensors on' to enable lm_sensors.
Actual Results: Starting lm_sensors: Starting lm_sensors: [ OK ]
Expected Results: Starting lm_sensors: [ OK ]
I'm submitting this as an initscripts bug, since my patch modifies /etc/rc.d/rc.
(BTW, the test at line 87 of /etc/rc.d/rc seems awfully hackish; is there really
not a better way?)
Created attachment 115881 [details]
Patch to /etc/rc.d/rc to special-case lm_sensors
BTW, PostgreSQL suffers from a similar problem on shutdown.
I can confirm this for postfix happening too. It is not high priority but it
also seems easy to fix. (and was not present in FC3)
This is one of these bugs that do not harm, but are pretty visible for user.
initscripts-8.42 has changed the "native service" detection, which fixes
lm-sensors and postfix.
Reassigning to postgresql.
Created attachment 140979 [details]
Make the init.d/functions inclusion detectable by /etc/rc.d/rc
This patch fixes the problem for postgresql.
Huh? That patch looks like a complete no-op to me. What is the underlying problem exactly?
if LC_ALL=C egrep -q "^..*init.d/functions" $i \
|| [ "$subsys" = "single" -o "$subsys" = "local" ]; then
action $"Starting $subsys: " $i start
". $INITD/functions" is not matched by the grep, so rc helpfully attempts to
provide the "starting postgresql" message and the "[ OK ]" status indication.
Eeek. I have to agree with Ian's original comment that there should be a better way. But at the same time
there's no particular use in the INITD variable in postgresql.init, so will comply in next turn.
I've modified postgresql.init in the latest packages for FC5 and up.