hardy init script status action

[Neal McBurnett]

On Tue, Mar 18, 2008 at 02:15:40PM -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.

I would see it as an advantage to be able to diagnose broken systems
by using status scripts.  This could be handled by snmp agents or ebox
or nagios scripts, or the like, perhaps in response to some other 
indications of problems.

This might not be the right time to add a status for udev, but unless
we think that udev being down would break things so badly that the
status command would not work, it makes as much sense to have a status
for udev as for other daemons.

As for the other daemons: given the simple nature and low risk of the
change, I'd rather be able to say from now on that status works, and
can be integrated in ebox etc, than to have to explain to folks for 5
years in our documentation etc. that "if you are on hardy, you need to
run this oddball script rather than using the lsb standard way of
querying the status".

Neal McBurnett                 http://mcburnett.org/neal/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20080318/dc89b031/attachment.pgp