Upstart config file generation

Mark Russell mark.russell at canonical.com
Wed May 4 18:07:31 UTC 2011


The Cookbook explanation might be helpful:

http://upstart.ubuntu.com/cookbook/#block-another-job-until-yours-has-started


On 05/04/2011 01:56 PM, Scott James Remnant wrote:
> I don't understand what you mean by this.
> 
> You will need to be more verbose in your explanation.
> 
> On Wed, May 4, 2011 at 10:53 AM, Clint Byrum <clint at ubuntu.com> wrote:
> 
>> Excerpts from Scott James Remnant's message of Wed May 04 09:48:09 -0700
>> 2011:
>>> Right, but this still doesn't explain what it does or why Upstart can't
>>> already do this.
>>
>> The issue is that upstart only blocks on goal changes, not on completion
>> of the goal.
>>
>> So if you have an OR condition, and the two things happen one after the
>> other, it has been my observation that the second event does not block,
>> because the goal is already 'start'.
>>
>> Its entirely possible that I misunderstood the problem I was having,
>> but this was the solution I came up with, and has been in place for
>> statd and portmap in Ubuntu for a while now.
>>
> 


-- 
Mark Russell | Mobile: +1 347 733 3211
Premium Service Engineer | Canonical, Ltd.
<mark.russell at canonical.com> | GPG: 4096R/B3BBA7D1

www.ubuntu.com | www.canonical.com



More information about the upstart-devel mailing list