Re: PROPOSAL: init file actions (draft 5)

[Shane Owenby <shane@raleigh.ibm.com>]

On Thu, Jun 24, 1999 at 06:55:53PM +0200, Dr. Werner Fink wrote:
> > > 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.
> > 
> 
> Simply `refresh' or `rescan' for the soft reload and `reload' for the
> forced version.
> 

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