UPSTART_EVENT and how to know why invoked

[Scott James Remnant]

On Fri, 2008-01-25 at 14:24 -0800, eehouse.org wrote:

> Let's say I have a job that gets stopped in a couple of ways:
> 
> stop on stopped foo
> stop on stopped bar
> 
You don't receive information about which events stopped you, since the
post-stop script should only clean-up the effects of the previous parts.

(Arguably the pre-stop script should receive this, but it's unclear to
me at the moment how to deal with conflicts between that information and
the information present in the job environment).

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

-------------- 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/upstart-devel/attachments/20080204/8e76da90/attachment.pgp