On Thursday, December 13, 2012 5:43:14 AM UTC-5, Matthew Burgess wrote: > > On Thu, Dec 13, 2012 at 12:41 AM, Ugo Bellavance > <[email protected]<javascript:>> > wrote: > > > I guess maybe I should ask to the Foreman group, > > but I was mostly wondering whether it was a good idea or not to restart > > puppet when changing puppet.conf. > > I think it would be a bad idea not to. Otherwise you've got a process > running under a different configuration than what is on disk, so when > it doesn't look like it's behaving like the config suggests it should, > it can cause a lot of head-scratching! > > That rises two questions in my mind:
1. In my understanding, puppetmaster catches any changes in the manifests without needing a restart, why can't the puppet client reload its puppet.conf parameters at the next run? 2. Why puppet can't use the "reload" option of most current daemons' init scripts? I think there should be a parameter "hasreload", similar to "hasrestart", saying that the init script supports the use of the "reload" argument. This would avoid this kind of problem, and people wouldn't have to redefine the restart command. Ugo -- 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/-/Vi0T1D5_sfwJ. 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.
