Bug 69138 - Init.d scripts: [force-]reload not consistend
Summary: Init.d scripts: [force-]reload not consistend
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: basesystem
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-18 07:44 UTC by Tobias Burnus
Modified: 2014-03-17 02:29 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2003-02-19 17:49:07 UTC


Attachments (Terms of Use)

Description Tobias Burnus 2002-07-18 07:44:02 UTC
Description of Problem:
 It is not clear what happens if one uses "force-reload" or "reload" when
 the daemon is not running. Basically two things happen: (a) the service
 is started and (b) nothing happens.
 Please try to be consistend and to try to find a common opinion with the
 Linux Standard Base. See gLSB-Bug
https://sourceforge.net/tracker/?func=detail&aid=568246&group_id=1107&atid=101107

Comment 1 Bill Nottingham 2003-02-19 17:49:07 UTC
At this point, this isn't somethign we'll change in house.

Comment 2 Tobias Burnus 2004-04-16 09:26:30 UTC
Current gLSB 2.0-pre version:
http://www.linuxbase.org/spec/book/LSB-generic/LSB-generic/iniscrptact.html

reload - cause the configuration of the service to be reloaded without
   actually stopping and restarting the service
force-reload - cause the configuration to be reloaded if the service
   supports this, otherwise restart the service if it is running

The "if it is running" makes clear that [force-]reload should not
start a service which is not running.


Note You need to log in before you can comment on or make changes to this bug.