Am 23.03.2014 09:57, schrieb Stefan Schulte:
> That's what I'd do, too. But you can use `creates` paramter to do the
> check, there is no need to invoke an external command.
>
> exec { 'create_mntpoint_/mnt/foo':
> command => '/bin/mkdir -m 0755 /mnt/foo',
> creates => '/mnt/foo',
> }
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.
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.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 1596666 (Ansage) 1149
*Email*: [email protected] <mailto:[email protected]>
*Skype*: dirk.heinrichs.recommind
www.recommind.com <http://www.recommind.com>
http://www.recommind.com
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/532FD65E.5000402%40recommind.com.
For more options, visit https://groups.google.com/d/optout.
<<inline: Logo.gif>>
