Well depending on complexity of your manifests, you could define a
service for puppet and require certain classes to be executed before
the puppet service is checked in order to avoid that problem.
At least for me it works, but I have to admit that this solution isn't
very pretty.
Example:
service { puppet:
require => [ class["class1"], class["class2"] ]
}
christian
On 22 Jun., 03:03, Patrick Mohr <kc7...@gmail.com> 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 defining puppet as a service and subscribing to
> puppet.conf is bad because it will stop puppet in the middle of a run which
> might make other subscribes not work.
>
> Anyone have advice? I don't want to put puppet in cron if I can avoid it.
> -Patrick Mohr
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
