Issue #7273 has been updated by Ryan Conway.
Hey there, Sorry for the long delay - I've been away. So, if the facts in our modules load in the same run, then that is fine, however we do make changes to the puppet.conf that need to also take effect immediately, for example delivering reports. Currently, as we try to notify the Puppet service, the agent then terminates as described above, and we have to manually handle this in our bootstrap script. It would be much cleaner and intuitive if Puppet could intelligently handle restarting itself in this situation, or had an option to re-parse and immediately re-run the catalog. What are your thoughts on that? ---------------------------------------- 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.
