On Jun 21, 2010, at 9:03 PM, Patrick Mohr wrote:
> Anyone have advice? I don't want to put puppet in cron if I can avoid it.
We did this:
service { puppet :
enable => true,
require => [ File['etc-sysconfig-puppet'],File['puppet.conf'] ],
subscribe => [ File['etc-sysconfig-puppet']
On Jun 22, 2010, at 2:43 AM, David Schmitt wrote:
> On 6/22/2010 3:03 AM, Patrick Mohr wrote:
>> I push out changes to puppet.conf using puppet. (I have gsh as a
>> backup for if I really screw things up, but I've never had to use it
>> yet.) Is there any safe and/or good way to restart puppet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, I've never had a problem with this.
If you wanted to be sure to run it right away after the current run, I
would use an exec to fire off an 'at' job for minutes in the future. Make sure to set
refreshonly => true on that exec.
Trevor
On 06/22/
On 6/22/2010 3:03 AM, Patrick Mohr wrote:
I push out changes to puppet.conf using puppet. (I have gsh as a
backup for if I really screw things up, but I've never had to use it
yet.) Is there any safe and/or good way to restart puppet after a
change is made o it's config? I'm assuming that just
I push out changes to puppet.conf using puppet. (I have gsh as a backup for if
I really screw things up, but I've never had to use it yet.) Is there any safe
and/or good way to restart puppet after a change is made o it's config? I'm
assuming that just defining puppet as a service and subscri
