[chef] Re: Re: push to restart notification to the end

[Haselwanter Edmund < >]

On 21.04.2011, at 15:55, Charles Duffy wrote:

All notifications are deferred unless explicitly marked :immediate

I know that :-) What I want is to ensure one of the deferred notification (or action) is the *last*

chef run

- send immediate stop to god

- change tomcat stuff

 -> notifies restart god

 -> notifies restart tomcat

- change apache stuff

it should not happen that tomcat is restarted *after* the god restart

cu edi

the last time I tried to solve this problem I had to restart (or start) god after the chef run.

cu edi

On Thu, Apr 21, 2011 at 8:28 AM, Haselwanter Edmund < "> > wrote:

Hi *,

Is there a best practice to push a restart notification to the very end. I do configure god watches
and want them to be run as the very last action. Maybe as last recipe in the node run_list which
ensures this? any examples on that?

cu edi
--
DI Edmund Haselwanter, "> , http://edmund.haselwanter.com/
http://www.iteh.at | http://facebook.com/iTeh.solutions | http://at.linkedin.com/in/haselwanteredmund

--

DI Edmund Haselwanter, "> , http://edmund.haselwanter.com/

http://www.iteh.at | http://facebook.com/iTeh.solutions | http://at.linkedin.com/in/haselwanteredmund