hardy init script status action

Dustin Kirkland dustin.kirkland at canonical.com
Tue Mar 18 05:23:59 GMT 2008


On Fri, 2008-03-14 at 16:39 +0000, Matt Zimmerman wrote:
> So long as, wherever possible, this uses more reliable methods (pid files,
> control sockets, etc.), I don't see a problem with the general design.

Yes, the pidofproc() function in /lib/lsb/init-functions is intelligent
in just such a way.


> There is always a chance of regression when modifying scripts which are
> critical for proper system functionality; for example, a typo in
> /lib/lsb/init-functions would be a very bad scene.
> 
> Be sure that each script is thoroughly tested after being extended in this
> way.

Fair enough.

A bug has been created with the proposed debdiff attached:
        https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/203169


> How many scripts do you plan to touch?  This could involve quite a few
> freeze exceptions, which, although low-risk, always require some additional
> effort on the part of the release managers, etc.

Once the status_of_proc() function is in /lib/lsb/init-functions, we
suggest unobtrusively adding a "status" handler to the init script
associated with these (9) common service daemons on Ubuntu Server
installations:
        * apache2, at, bind9, cron, dovecot, openssh, samba, sysklogd,
        udev


:-Dustin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20080318/54b9f08e/attachment.pgp 


More information about the ubuntu-devel mailing list