Bug 69138

Summary:	Init.d scripts: [force-]reload not consistend
Product:	[Retired] Red Hat Linux	Reporter:	Tobias Burnus <tobias.burnus>
Component:	basesystem	Assignee:	Bill Nottingham <notting>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	rvokal
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-02-19 17:49:07 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:

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.