Red Hat Bugzilla – Bug 98470
install_initd: Support "Should-Start" and "Should-Stop"
Last modified: 2014-03-16 22:37:11 EDT
It would be nice if install_initd would support the Should-Start/Stop header
introduced in gLSB 1.9. This is a nice feature and already used by the first
appliations (http://xprint.mozdev.org) and SuSE/UnitedLinux have used it also
for their init scripts (there X-UnitedLinux-Should-Start/Stop called). (Debian's
lsb.deb has also support for Should-Start/Stop :-)
The specification can -- as always -- found on the Linux Base server:
- Green marked diffs:
- Current "Work in Progress":
- gLSB Specs (1.9 freeze: 3 July 2003; spec auth approval: 8 August;
LSB 1.9 is not used for certification but paves the way for LSB 2.0):
If you have doubts, send an mail to firstname.lastname@example.org
New URL (no longer part of the WIP, now in 1.8.030702, to become 1.9):
Bill-what are your thoughts. Should this bug remain open?
It's unlikely to happen without a patch appearing. It's not a required part of the spec.
Actually, leaving open. But the comments about when it will be handled still apply.
Created attachment 397310 [details]
patch to support Should-Start/Stop
This is a simple patch against 1.3.44 to detect Should-Start/Stop header entries and use them for weak dependency resolution.
Merged in http://git.fedorahosted.org/git/?p=chkconfig.git;a=commitdiff;h=25382cccc47e853d78ec3ca92de345ed5164433b (although it's then been later cleaned up to not cut-and-paste the same code so much.)
Thanks for the patch, will be in 1.3.45-1.
chkconfig-1.3.45-1.fc13 has been submitted as an update for Fedora 13.
chkconfig-1.3.45-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.