Issue #7273 has been updated by Daniel Pittman.
On Fri, Jul 8, 2011 at 13:37, <[email protected]> wrote: > 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. Actually, we have explicit direction that the Puppet core *MUST* be able to change the `run mode` dynamically, which implies that we are able to make sweeping changes to configuration on the fly. So, in the longer term any problems that would make this hard to achieve would need to be resolved anyhow. Obviously, that doesn't move our timeline around for doing it, but I think this is probably only a short-term issue. (…and don't get me wrong, I don't think that this is a trivial thing to change; at the very least, logging and other dynamic data will have to be audited as part of this change to make sure they notice the dynamic updates and all!) ---------------------------------------- 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 More Information Priority: Normal Assignee: Nigel Kersten 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.
