> I was hoping that there was a way for Puppet to remember the
> subdirectories and only chmod on new subdirectories that are not mode
> 700...
>
> or if that is too complicated to support internally, then something
> simple like:
> If file{} had globbing ability, then
> [pseudo] file { "/foo/*": ... }
> for item in /foo/*
> if item is not a directory: then continue
> if item mode != 700: then chmod 700 item
>
Thus the server doesn't know what files the client has, so it can't
presently do that -- it couldn't build the resource graph.
Exec in your usage may feel like the thermonuclear option, but you're using
it in a fairly limited way... be sure it's executed with a require in the
right
place in the dependency chain and it's not too unreasonable IMHO, as it's
not a resource intensive command.
It's there to fill in the gaps for things that are hard to model.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
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.
