On Mon, 10 May 1999, Balazs Scheidler wrote:
> > Shouldn't that use `/etc/init.d/apache reload' instead? Most things,
> > as far as I know, will work that way, sed -e 's/apache/$DAEMON/'. I
> > think it would be good to display the /etc/init.d/* method in this
> > policy item, as a way of documenting that feature of the sysvinit
> > scripts, which provide a standard interface to reloading any daemon.
>
> hmmm... I agree with you here. That example was intended to show the usage
> of logrotate, not meant to show the way of restarting a daemon.
>
> So the line "kill -HUP `cat /var/run/apache.pid`" should read:
>
> /etc/init.d/apache restart
'restart'? Why not 'reload'? If you meant 'reload', use 'force-reload'
instead.
>From Debian Policy Manual, section 3.3.2 ('Writing the scripts'):
<quote>
Packages can and should place scripts in `/etc/init.d' to start or
stop services at boot time or during a change of runlevel. These
scripts should be named `/etc/init.d/<package>', and they should
accept one argument, saying what to do:
`start'
start the service,
`stop'
stop the service,
`restart'
stop and restart the service,
`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.
The `start', `stop', `restart', and `force-reload' options must be
supported by all scripts in `/etc/init.d', the `reload' option is
optional.
</quote>
Remco
--
rd1936: 10:00pm up 8 days, 5:56, 7 users, load average: 1.48, 1.51, 1.56
