Hi, On 03/24/2014 07:53 AM, Dirk Heinrichs wrote: > But that's not the OP's problem. Creating the mount point can be > perfectly accomplished with a file resource. The problem is to adjust > permissions AFTER mounting something there w/o having to wait for the > next agent run.
the point of using the exec for creating the directory is to have the file resource *require* the mount, not vice versa. You really don't get around managing the directory with two resources in this scenario, one exec and one file. > If the permissions of the mount point and the mounted directory are > different, that would lead to a permission change ping-pong, unless one > leaves the permission and ownership attributes of the mount point file > resource untouched and uses an exec with appropriate conditions and > "refreshonly=>true", triggered by the mount resource. Refreshonly is mostly a Bad Idea. The creates parameters in Stefan's code makes sure that the command is run exactly once (except the mountpoint gets deleted, then it will have to run again). >From that point on, the permissions will only ever be managed by the file resource. Cheers, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/532FFE44.9050007%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
