Bug#60979: What /etc/init.d/xxx restart does?
On Fri, Sep 13, 2002 at 07:22:39AM +0100, Oliver Elphick wrote:
> On Fri, 2002-09-13 at 02:50, Chris Waters wrote:
> > It tells you by its silence -- if the service actually had started or
> > stopped, then it would have printed a message.
> But the Unix norm is that silence means success. Failure produces a
> message.
Well, yes, that's the norm for normal commands, but these aren't
normal commands. They aren't in anyone's path, and under normal
circumstances, they're only called indirectly by init when you change
runlevels. And I believe the idea is that when you change runlevels,
you want to know which services start or stop, but don't really care
about those that continue running (or not running) uninterrupted.
--
Chris Waters | Pneumonoultra- osis is too long
xtifr@debian.org | microscopicsilico- to fit into a single
or xtifr@speakeasy.net | volcaniconi- standalone haiku
Reply to: