Issue #7273 has been updated by Ryan Conway.
Hey, I think the issue we have with that is we can't wait an hour for the next run in order for the changed settings to take effect and any remaining settings be applied, as we're using Puppet for servers that autoscale on EC2 as well. So they need to run their whole config successfully in one run. We work around this problem at the moment, but would be nicer if Puppet could handle restarting itself when you notify the Puppet service if that is possible? ---------------------------------------- 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: Investigating 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.
