Re: PROPOSAL: init file actions (draft 5)

[Jim Knoble <jmknoble@pobox.com>]

The problem with only supporting `reload configuration iff supported'
(the graceful or soft one) and `restart the service regardless of
whether it can be gracfully reloaded' is that it takes actual knowledge
of whether the service can gracefully reload in order to determine
which to use.  `reload if supported, otherwise restart' doesn't require
operator knowledge (where the `operator' is not necessarily a human one).

--jim

%%%%%%%%%%%%%%% jim knoble %%%%%%%% jmknoble@pobox.com %%%%%%%%%%%%%%%%%

På 1999-Jun-24 klokka 13:41:57 -0400 skrivet Shane Owenby:

: What is the 'force-reload' option doing that the 'restart' option doesn't
: already do? They both _force_ the daemon to reload its configuration.
: 'restart' stops and then restarts the daemon    and 'force-reload' seems to
: do the same thing.....if the daemon supports a dynamic configuration
: change (like Apache) then the 'reload' option can be used....
: 
: So can anyone give an example where the below will not work?
: 
: Thanks
: Shane Owenby
: shane@raleigh.ibm.com
: 
: 
: Init files should accept one argument, saying what to do:
: 
: start
:      start the service,
: 
: stop
:      stop the service,
: 
: restart
:      stop and restart the service if the service is already running,
:      otherwise start the service
: 
: graceful (or reload or graceful-restart )
:      cause the configuration of the service to be reloaded without
:      actually stopping and restarting the service, if the service is not
:      running it is started
: 
: status
:      return (and optionally display) the current status of the service