Re: PROPOSAL: init file actions (draft 5)

["Dr. Werner Fink" <werner@suse.de>]

> > > > 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?

Some services (e.g. snmp) do not have the possibility to rescan their configuration
at runtime but the admin doesn't want to restart the service with the new
configuration, e.g. to avoid to kick out some running sessions/requests.


          Werner