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 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. > > Puppetd does reload its configuration automatically when the config file > changes. Any settings that do not get reloaded should be considered bugs and > reported to the bug tracker. >
It seemed to me that adding report=true to [puppetd] using augeas didn't cause puppetd to start sending reports each run. I'll check to see that's actually true later today. -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.
