General discussion about Chef

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


Chronological Thread 
  • From: "Jason J. W. Williams" < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Force service start at end of recipe.
  • Date: Tue, 17 May 2011 10:42:19 -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=tbHqnwEAr/ibyozQAWBS9QiRL8x8L8ZDoFmjcqOYnaS636cLbGrdii/jZJYzlwWHBF QFTicYpbTpKtrqcuw9s7lGknncSKGZWvHGVsRHmkvufP+pMcPoXKnJK5pVbyYVNxOiK+ S/qnV3BD4BrHbuFXV/92AlY+dJVUOPxc1ui3M=
Hi Adam,

On Fri, May 13, 2011 at 10:47 PM, Adam Jacob 
< >
 wrote:
> An easier way would be to just call the code that's in the ticket I
> linked earlier, so that the new data is available instantly.

That doesn't appear to be a solution for changing nsswitch.conf. I've
added the following to my ldap_auth recipe (along with a notifies
trigger on the nsswitch.conf template definition):


ruby_block "reset nss lists" do
  action :nothing
  block do
    Etc.endgrent
    Etc.endpwent
  end
end

While those calls close /etc/group and /etc/passwd forcing a reload of
their contents, they don't force a reload of nsswitch.conf...which is
what is needed for the NSS libraries to pickup that they need to start
looking in LDAP.

-J

Archive powered by MHonArc 2.6.16.

§