Bug 98470

Summary: install_initd: Support "Should-Start" and "Should-Stop"
Product: [Fedora] Fedora Reporter: Tobias Burnus <tobias.burnus>
Component: chkconfigAssignee: Bill Nottingham <notting>
Status: CLOSED ERRATA QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: mitr, poelstra, rvokal
Target Milestone: ---Keywords: FutureFeature, Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://www.linuxbase.org/~gk4/wip-sys-init.html
Whiteboard:
Fixed In Version: chkconfig-1.3.45-1.fc13 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-04 15:36:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch to support Should-Start/Stop none

Description Tobias Burnus 2003-07-02 18:47:13 UTC 
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:
  http://www.linuxbase.org/~gk4/wip-sys-init.html

- Current "Work in Progress":
  http://www.linuxbase.org/spec/wip/wip/initscrcomconv.html

- 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):
  http://www.linuxbase.org/spec/

If you have doubts, send an mail to lsb-discuss
Comment 1 Tobias Burnus 2003-07-23 20:55:40 UTC 
New URL (no longer part of the WIP, now in 1.8.030702, to become 1.9):
  http://www.linuxbase.org/spec/gLSB/gLSB/initscrcomconv.html
Comment 2 John Poelstra 2008-07-02 19:24:27 UTC 
Bill-what are your thoughts.  Should this bug remain open?
Comment 3 Bill Nottingham 2008-12-04 19:57:14 UTC 
It's unlikely to happen without a patch appearing. It's not a required part of the spec.
Comment 4 Bill Nottingham 2008-12-04 19:57:45 UTC 
Actually, leaving open. But the comments about when it will be handled still apply.
Comment 5 Iain Arnell 2010-03-02 12:32:46 UTC 
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.
Comment 6 Bill Nottingham 2010-03-04 15:36:53 UTC 
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.
Comment 7 Fedora Update System 2010-03-04 15:49:05 UTC 
chkconfig-1.3.45-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/chkconfig-1.3.45-1.fc13
Comment 8 Fedora Update System 2010-03-11 13:27:23 UTC 
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.