upstart at ser1.net
Mon Oct 9 20:55:26 BST 2006
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?
As I said, the other two cases have fairly straightforward behavior.
Does Upstart generate an event when a job goes into a wait state? If it
did, then there'd be an obvious solution for #2, too. If it is a
conditional dependency, and it generates a "wait", then consider the
requirement as satisfied. "Conditional" really should mean "I don't
need this to start, but it would be nice to have."
Are there any cases I'm missing that could result in unexpected
> > Finally, would somebody with write access to the main Upstart page
> Have done so.
This e-mail (including any attachments) is intended only for the recipients named above. It may contain confidential or privileged information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please notify the sender of that fact and delete the e-mail from your system.
More information about the Upstart-devel