Please have a look at the wikipage
and change your initscripts to comply with the LSB standard.
Especially check the exit status and add a LSB Header.
E.g. starting a service should return with 0, if the service is already running and stopping a stopped service should also return with 0.
Also check, if your service has to be _on_ per default, and turn it off in the old chkconfig line, if not.
fixed in -3.fc8. I'm skipping the implementation of reload/try-restart/etc as
those all just map to the restart operation anyway. Thanks!
Was this ever fixed? Should the script really exit with code 0 if it's not run
as root, if networking is down, the irqbalance binary is missing or if the lock
file exists? From /etc/init.d/irqbalance:
# Check that we're a priviledged user
[ `id -u` = 0 ] || exit 0
# Check that networking is up.
if [ "$NETWORKING" = "no" ]
[ -f /usr/sbin/irqbalance ] || exit 0
if [ -n "$ONESHOT" -a -f /var/lock/subsys/irqbalance ]; then
Apparently this was fixed on Redhat:
"if networking is down" ???
why does irqbalance rely on networking???
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.
If this bug still exists in rawhide, please change the version back to
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)
Thanks for your help and we apologize for the interruption.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
As this bug is in MODIFIED, Fedora believes that a fix has been committed that resolves the problem listed in this bug report.
If this is not the case, please re-open this report, noting the version of the package that you reproduced the bug against.
Thanks for the report!