Issue #7273 has been updated by Nigel Kersten.
I'm torn here, but agree with Noah that there are good reasons to push out a new puppet config file that doesn't take effect until the start of the next run. A common solution here for people is to have a distinct set of manifests just for setting up Puppet itself, whether that is with an environment or tags. They then schedule Puppet to run once to bootstrap itself, and once for the real config. What about sending a SIGHUP to the puppet agent process? Doesn't that do what you need? ---------------------------------------- Bug #7273: Modifying puppet.conf causes 'reparsing config' and TERM signal results in shutdown of daemon https://projects.puppetlabs.com/issues/7273 Author: Randall Hansen Status: Needs Decision Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: ... waiting for details from Ryan Conway ... -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
