[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: notifies on resource not notifying


Chronological Thread 
  • From: Daniel DeLeo < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: notifies on resource not notifying
  • Date: Thu, 3 Jan 2013 10:25:14 -0800


On Wednesday, January 2, 2013 at 3:24 PM, Seif Attar wrote:



On 2 January 2013 22:20, Daniel DeLeo < " target="_blank"> > wrote:
Is this with a pristine copy of Chef? I'm curious as to how you're ending up with owner, group, and mode set on that resource. The code you were looking at before would do that (File#load_current_resource_attrs), but it should be skipped on windows.

I installed chef on the vm using the msi installer and haven't modified the code in anyway if that is what you mean by pristine.
Then can you try commenting out that method? That's the only place I can think of where you'd be getting unix-style permissions attributes getting set on your resource.
 

It is all mind boggling to me, because it install and executes fine when I remove the if statement that checks if the file exists in the workaround, which is why I assumed what I am doing with the if statement is wrong :S

Maybe it helps unravel the mystery




-- 
Daniel DeLeo




Archive powered by MHonArc 2.6.16.

§