Description of problem: /etc/sysconfig/quagga defines QCONFDIR init.d scripts explicitly specify /etc/quagga instead of using it. Version-Release number of selected component (if applicable): quagga-0.98.6-5.el5_5.2 How reproducible: as installed Steps to Reproduce: 1. 2. 3. Actual results: Expected results: The init.d scripts should all use QCONFDIR rather than an explicit path since they all include /etc/sysconfig/quagga. Additional info: Also applicable to 0.99.18 on Quagga site in source: redhat/quagga.sysconfig. Would have (still might) open a bug there too, wasn't sure where the redhat pieces originate.
Quagga folks will accept the change if it comes from you folks: https://bugzilla.quagga.net/show_bug.cgi?id=657 Denis Ovsienko <infrastation> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://bugzilla.redhat.com | |/show_bug.cgi?id=716324 --- Comment #1 from Denis Ovsienko <infrastation> 2011-07-12 21:20:40 MSD --- The files in redhat directory are primarily used by RedHat builds, if they update these files, I can merge the change upstream.
Created attachment 557674 [details] The patch introduces usage QCONFDIR in initscripts
(In reply to comment #0) > Additional info: > Also applicable to 0.99.18 on Quagga site in source: redhat/quagga.sysconfig. > Would have (still might) open a bug there too, wasn't sure where the redhat > pieces originate. I don't think. Versions using current 0.99.20 (and future releases) have replaced initscipts by systemd. There should be delivered unit files to upstream. There could be opened extra bug for RHEL-6. The patch attached above is not applicable to RHEL-6 'as is'.
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