> Questions : is this the proper way to get a .repo out onto the client > machine?
There is a resource type specifically for this. http://docs.puppetlabs.com/references/stable/type.html#yumrepo > And... what's causing this error message? You probably wanted the refreshonly => true attribute on that exec - so it would only run when the file was updated (ie. the notify would force it to run). At the moment its always going to run which is probably not what you intended. What happens when you run yum makecache on the command line? Perhaps there is a mistake somewhere. Puppet won't show you the command output by default ... so try running it yourself and seeing what the problem is. Also - as far as the 'cache' not being cleared even after you removed the exec block .... I'm guessing you've tried touching the /etc/puppet/ manifests/site.pp file, or restarting your puppet master? The exec might still be cached on the server perhaps? ken. -- 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.
