> file { "/usr/src/php":
> ensure => directory,
> }
>
> This results in /usr/src/php being created as mode 400. One could argue
> this is not a bug since 400 is the default mode. However on its second
> run puppet changes the mode on this dir to 500. So either the initial
> mode or the later change is clearly a bug. :-)
This is a feature. Puppet assumes +x when a directory gets +r. This is
helpful for setting modes recursively for both dirs and files.
The other thing looks fishy, though. I noticed the effect in conjuction
with bind-mounts (i.e. setting mode on a mount point), but accepted it
as a fact in that case. Changing modes of symlink targets at the time of
symlink creation may be somehow intended, but it sure is
counter-intuitive. I call possible bug.
Regards,
Felix
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
