sysklogd-1.4.1-26_EL 1. /sbin/chkconfig syslog off 2. Update sysklogd 3. Check output of /sbin/chkconfig --list syslog syslog should still be disabled, but isn't. the postinstall script of sysklogd should check for the value of "$1" before running "chkconfig --add syslog"
That's not a sysklogd bug, that would be a chkconfig bug. sysklogd is fine.
Created attachment 125221 [details] patch for this issue Here's the patch for this issue; in local testing it has passed through newly-added RHTS tests and the old tests.
I just upgraded from version 1.3.13.2 to 1.3.13.3 of chkconfig. In the latest version (but not in the previous version), "chkconfig --levels 45 on" will also turn on those levels that are specified as being on by default. My guess this is a different sympton of the same problem already described above.
"Me Too!" re comment #5. We have a process that recovers certain custom settings after an o/s reload. It's broken in RHEL 4.0 update 3. It looks like chkconfig has changed its method of operation; or at least it doesn't behave the way I read the man page. I just confirmed it works as expected on RHEL 3.0 and on RHEL 4.0 update 2. The daemonrecover script would get each selection and turn it on and off based on the /etc/netdata/daemons/chkconfig.conf file. Here's a code snippet: + chkconfig --level 1 netfs on + chkconfig --level 2 netfs off + chkconfig --level 3 netfs on + chkconfig --level 4 netfs on + chkconfig --level 5 netfs on Here is what appears to happen: root > chkconfig netfs reset root > chkconfig --list netfs netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off root > chkconfig --level 1 netfs on root > chkconfig --list netfs netfs 0:off 1:on 2:off 3:on 4:on 5:on 6:off root > chkconfig --level 2 netfs off root > chkconfig --list netfs netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off root > chkconfig --level 3 netfs off root > chkconfig --list netfs netfs 0:off 1:off 2:off 3:off 4:on 5:on 6:off root > chkconfig --level 1 netfs on root > chkconfig --list netfs netfs 0:off 1:on 2:off 3:on 4:on 5:on 6:off It's like it resets the configuration for anything you don't specify on the chkconfig --level line to its default.
I want to add that I have confirmed that when using drbd and heartbeat rpms when turning off drbd, heartbeat turns on and when turning off heartbeat drbd turns on. When using this patch, that does not happen. That is with version chkconfig-1.3.13.3-2. Not sure if it also affects other scripts in init.d or not ... but I think it is pretty major if using "chkconfig service1" effects service2
This issue is on Red Hat Engineering's list of planned work items for the upcoming Red Hat Enterprise Linux 4.4 release. Engineering resources have been assigned and barring unforeseen circumstances, Red Hat intends to include this item in the 4.4 release.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0286.html