[chef] RE: Re: Re: Windows Chef-Client-Lastest.msi 10.12.0 - Changes & Bug

[Wade Peacock < >]

I can deal with the change to C:\chef as long as the next chef-client-lastest.msi continues to use it. One fear I have is that the next msi goes back to \etc\chef or even a different directory. Currently we only have 25 Windows systems using chef-client to control configurations, however we have another 100+ system which we'll be adding gradually over the next while and having a moving default folder will become problematic. While is possible to path the client configuration file to use via the command like chef-client -c <path_to file>\client.rb   it is easier to if just chef-client is needed.

 

W

 

From: Paul Morton - BIA [mailto:
Sent: Tuesday, June 26, 2012 5:22 PM
To:
Cc:
Subject: [chef] Re: Re: Windows Chef-Client-Lastest.msi 10.12.0 - Changes & Bug

 

+1 for c:\chef.   

 

/etc and /var are filesystem litter on windows.

On Jun 26, 2012, at 5:16 PM, "Tim Smith" < "> > wrote:

Can we please keep the default path at C:\Chef.  Nothing should be in an etc directory on a Windows box.

 

 

From: Wade Peacock < "> >
Reply-To: " "> " < "> >
Date: Tuesday, June 26, 2012 4:30 PM
To: " "> " < "> >
Subject: [chef] Windows Chef-Client-Lastest.msi 10.12.0 - Changes & Bug

 

Hi All,

 

Firstly for those who use Windows 2003 Systems the new chef-client-lastest.msi (10.12.0) still contains this bug I reported for 0.10.8:

 

http://tickets.opscode.com/browse/CHEF-2851 

 

Secondly, the default search path for chef-client is C:\Chef\ instead of <drive your on>:\etc\chef. Looking it to C drive is good. Dropping  etc out of the path is inconvenient.

 

http://tickets.opscode.com/browse/CHEF-3244

 

 

Wade Peacock
Production IT | Vision Critical
direct  604.629.9358

mobile  604.363.8137

 

www.visioncritical.com

New York  |  London  |  Vancouver|  Paris  | Sydney  |  Chicago |  San Francisco | Toronto | Montreal | Calgary