On Wednesday, January 16, 2013 3:35:46 PM UTC-6, Josh Cooper wrote:
>
> Hi Alex, 
>
> On Wed, Jan 16, 2013 at 12:49 PM, phundisk 
> <[email protected]<javascript:>> 
> wrote: 
> > I am noticing some very odd behavior with my puppet server and a windows 
> > client. 
> > 
> > For my puppet server I have a module setup similar to this below... 
> Please 
> > note, I am not setting any permission on this file. 
> > file { "C:\\directory\\file.dll": 
> >                 ensure => 'present', 
> >                 source => "puppet:///modules/aaa/file.dll", 
> > } 
> > 
> > The actual permissions in the unix filesystem is set to 644 
> > 
> > When I apply this to my Windows client, the puppet agent will change the 
> > mode of the file already on the server to 0644, which is not what I 
> would 
> > expect puppet to do.  I would expect since it is already there, it would 
> not 
> > even care about the permissions. 
> > 
> > I know this is taking the UNIX filesystem permissions because I chmod'd 
> the 
> > file on the filesystem to 0777 and when running puppet on Windows, it 
> took 
> > the new permissions. 
> > 
> > This becomes problematic because I am using puppet environments with an 
> SVN 
> > checkout system.  Every time I update svn checkouts, it defaults to 
> 0644. 
> > Does anyone know if this is expected behavior or ways around this? 
>
> This is "expected" in that windows agents emulate current *nix agent 
> behavior. With that said there are issues with the current behavior in 
> general. Currently, *nix agents will attempt to apply the remote 
> uid/gid to the local system, which may not be what you would expect. 
> See http://projects.puppetlabs.com/issues/5240. 
>


What I would expect on both Unix and Windows is that if the target file 
already exists and the resource declaration does not specify a mode, then 
the current mode will not be changed.  It is not a managed property.  The 
same applies to uid/gid.  This is distinguished from the case of issue 
5240, which is about the uid/gid to apply to a File resource if the target 
file is initially absent.

Is the Windows client indeed emulating the Unix one here?  In other words, 
are they *both* buggy, or is it just the Windows client?


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/b3WN5RZXVWwJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to