Scott James Remnant scott at
Mon Oct 9 22:33:24 BST 2006

On Mon, 2006-10-09 at 15:55 -0400, Sean Russell wrote:

> On Monday 09 October 2006 13:43, Scott James Remnant wrote:
> >> 2) A job goes into a perpetual "wait" state.  The
> > > only way these could be handled is by time-out, but that's a really
> > > bad solution.
> ...
> > Can you provide any actual use cases for #2?  I've had a think and
> > can't actually think of any.
> No, but just because I can't think of one doesn't mean that it can't 
> occur -- and that's my concern.  Upstart allows jobs to go into a wait 
> state; therefore, it is possible for someone to define a job that 
> conditionally depends on a "waiting" job.  The question is: how do you 
> handle that case?
> Does Upstart generate an event when a job goes into a wait state? 
Yes, upstart generates events at all job state changes.

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 : 

More information about the Upstart-devel mailing list