hardy init script status action

[Matt Zimmerman]

On Tue, Mar 18, 2008 at 06:51:03PM +0000, Scott James Remnant wrote:
> On Tue, 2008-03-18 at 14:15 -0400, Mathias Gug wrote:
> 
> > On Tue, Mar 18, 2008 at 06:06:50PM +0000, Scott James Remnant wrote:
> > > On Tue, 2008-03-18 at 14:02 -0400, Mathias Gug wrote:
> > > 
> > > >  * Add a status action to the init script for the following 9 packages:
> > > >     apache2, at, bind9, cron, samba, dovecot, openssh, sysklogd, udev
> > > > 
> > > A status argument for the udev init script is absolutely pointless.
> > > 
> > > If it's not running, your system is broken.
> > 
> > I've added udev to the list because there is udevd running on my system.
> > If you think it's pointless, that is one less package to touch.
> > 
> Why do you need to know the status of daemons?  Are you writing some
> kind of front-end?

It is useful to have a programmatic interface for this, for example for
monitoring, system administration scripts, etc.

> If you can use ps to see the daemons running, aren't you inherently
> giving yourself the answer?

This is, as you realize, sufficient for a human, but not a program.

-- 
 - mdz