General discussion about Chef

[chef] Force service start at end of recipe.


Chronological Thread 
  • From: "Jason J. W. Williams" < >
  • To: " " < >
  • Subject: [chef] Force service start at end of recipe.
  • Date: Fri, 13 May 2011 10:57:57 -0600
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:content-type:x-mailer:message-id:date:to :content-transfer-encoding:mime-version; b=qbg4ZJkjSGOUvEelRbyWiW+uwTJO3yv9UHaheABUhY5F8KrgSVur5fxsQjRL5HsiAX uwdeeEkrQhQauCWuxmyZ42bFsf8v06z/u1gAYrbtW4M0AwrRQ4kVGHChEHAzRmjS7WVB TZjtyDjiBJYeFL9lcOLPNKXEYxliR3y/JSxOM=
Besides putting :immediately on the service restart notifies in the template 
commands, is there a way to force a new service to start at the end of a 
recipe? 

My problem is I have a recipe that correctly installs ldap authentication for 
the OS, but since it doesn't immediately start the client daemon, subsequent 
recipes fail when they reference users defined in the ldap directory. Any 
pointers are greatly appreciated. 

-J

Sent via iPhone

Is your e-mail Premiere?

Archive powered by MHonArc 2.6.16.

§