Re: RFC init.d actions [force-]reload and non-running programs
Previously Henrique de Moraes Holschuh wrote:
> Debian policy says:
> cause the configuration to be reloaded if the service
> supports this, otherwise restart the service.
> So it is badly defined in policy, and behaviour is not determined if the
> service supports reloading, but it is not started.
How is that unclear? configuration reloading should be obvious,
and since you can't restart something that hasn't been started
the rest is just as obvious.
/firstname.lastname@example.org This space intentionally left occupied \
| email@example.com http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com