[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Force service start at end of recipe.


Chronological Thread 
  • From: "Jason J. W. Williams" < >
  • To: Adam Jacob < >,
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Force service start at end of recipe.
  • Date: Tue, 17 May 2011 16:04:58 -0600
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=n99LByr2cEmnnmYHgHFaCq1DQ02swVsTDctITbix7mYv6IfUiQHaj2WvB2VxB6dwJt iD8yMcLPJkmo4rXp6TYgpy41HsCbvr2YpNHjRqsY98vNTvnPKZU0nC00wZpJmDo/fH5n PTC4SQHPOGU18KE+Ot72obIxSsPRmYN9TAyE8=

Running 'exec "chef-client"' inside the ruby_block gets further,
except what the original chef-client process was doing with apt
doesn't seem to release /var/lib/dpkg/lock causing the first recipe
that hits an debian package in the new process to fail.

-J

On Tue, May 17, 2011 at 3:53 PM, Jason J. W. Williams
< >
 wrote:
>> Yeah, I expect one of those - what happens to the child that forks? Does
>> it complete the run?
>
> Doesn't look like it:
>
> IOError: Cannot open or read
> /var/cache/cookbooks/python-essentials/attributes.rb!
> FATAL: Stacktrace dumped to /var/cache/chef/chef-stacktrace.out
>



Archive powered by MHonArc 2.6.16.

§