On Thursday, November 29, 2012 1:40:01 AM UTC+11, jcbollinger wrote:
>
> So you're saying that *none* of the collected Execs are running? In that
> case, check the cached catalog to see whether it contains those Execs at
> all. That will establish whether it is a problem with resource collection
> or with the individual resources. It should also allow you to verify the
> resource parameters.
>
> As for the individual resources, you would be well advised to use curly
> brackets around variable names inside strings. Especially, you should use
> them in "/srv/mnt/.${hostname}_commvault_backed_up" and similar strings
> (else Puppet will think you want the variable named
> $hostname_commvault_backed_up), but it's a good habit to use curly brackets
> in every variable reference.
>
> Actually, the brackets are probably your issue: you presumably don't
> define a variable named $hostname_commvault_backed_up, so it interpolates
> as nothing. That means what you've written is equivalent to "creates =>
> '/srv/mnt/.'", which is in turn equivalent to "creates => '/srv/mnt'".
> Since that directory already exists, applying the Execs will not result in
> their commands running.
>
>
Of course! Thanks for that John, you are correct. I was having these
problems because I hadn't used braces in the use of the variable. When I
changed that, I got the behaviour I expected.
Thanks!
Geoff
--
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/-/q_xaX5fPFBwJ.
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.
