/etc/init.d/* status .. what to do when transitioning to an upstart job?

[Kees Cook]

Hi,

On Wed, Dec 15, 2010 at 12:39:50PM -0800, Clint Byrum wrote:
> One thought that Dustin Kirkland had was to ehnance the 'service'
> command to look in a directory for shell snippets, something like
> 
> /etc/service/status.d
> 
> And if one exists for the job name, run it, otherwise just run the
> upstart status and provide an LSB compatible return code.
> 
> This would also allow for the post-start stanza to call the same code if
> it is needed.
> 
> Does anyone have strong thoughts on this? Given the service.d approach,
> it would seem the correct course of action is to open a feature request
> against sysvinit, document it in our upstart job writing best practices,
> and to document this feature in the server guide.

Why should this be external to upstart? This seems to me like a clearly
missing feature in upstart itself. (i.e. a "status" stanza for services
that need a non-passive check.)

-Kees

-- 
Kees Cook
Ubuntu Security Team