Description of problem: Quagga daemons (e.g. zebra, ospfd) write pidfiles under /var/run/quagga. These pidfiles are not removed when the daemons are stopped. Version-Release number of selected component (if applicable): quagga-0.98.6-5.el5 How reproducible: Always Steps to Reproduce: 1. service zebra start 2. service zebra stop Actual results: The pidfile (/var/run/quagga/zebra.pid) remains after "stop". Expected results: The pidfile should be deleted upon stopping the service. Additional info: The killproc function in /etc/rc.d/init.d/functions is looking for /var/run/zebra.pid if no pidfile was explicitly passed with -p. Could either pass the pidfile to killproc: @@ -35,7 +35,7 @@ ;; stop) echo -n $"Shutting down $prog: " - killproc zebra + killproc -p /var/run/quagga/zebra.pid zebra RETVAL=$? [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/zebra echo ... or configure quagga with pidfiles under /var/run.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0050.html