[chef] Re: Re: Re: Re: chef-client first run


Chronological Thread 
  • From: Alan Thatcher < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: chef-client first run
  • Date: Sun, 23 Aug 2015 21:50:43 +0000

:( no way I can go back that far. Just curious as to why, as in does it cause some mischief I'm just not comprehending. If not, Is there a way to monkey patch it besides putting something in rc.local or the like. If I changed the init script it would just overwrite it on the next run.

On Sun, Aug 23, 2015 at 4:26 PM Lamont Granquist < "> > wrote:

It was changed in 12.0.0

See https://github.com/chef/chef/issues/3305


On 08/23/2015 06:02 AM, Elias Abacioglu wrote:
I gave my votes to it..

Well I know it wasn't like this before.
So does anyone know when this "feature" was implemented so I can install the client version before that?

2015-08-22 6:13 GMT+02:00 Alan Thatcher < " target="_blank"> >:
I made a enhancement request here: https://feedback.chef.io/forums/301644-chef-product-feedback/suggestions/9435582-chef-client-12-4-1-should-run-when-started-as-o

-Alan



On Fri, Aug 21, 2015 at 10:50 AM Alan Thatcher < " target="_blank"> > wrote:
I'm starting with 12.4.1, but I was just wondering about this yesterday. When a node reboots and the chef-client starts, it would be my preferred behavior that it runs then and not just queue until the interval has elapsed.

On Fri, Aug 21, 2015 at 10:41 AM Elias Abacioglu < " target="_blank"> > wrote:
Hi,

I've just upgraded to chef-client 12.4.1.

One thing I noticed is that when I start the client in daemon mode is that it doesn't do the chef run until the interval time has expired.
So every time the service is restarted, it takes 30 minutes before chef is executed.
Is there a setting to make it execute when it's first started?


/Elias





Archive powered by MHonArc 2.6.16.

§