Issue #2239 has been updated by Todd Zullinger.
This is perhaps a bit loosely related, but currently puppetmasterd doesn't handle a SIGHUP well. <pre> Jul 26 19:09:20 inocybe puppetmasterd[30458]: Caught HUP; calling restart Jul 26 19:09:20 inocybe puppetmasterd[30458]: Restarting with '/usr/sbin/puppetmasterd ' </pre> It logs that it received the HUP, but fails to reload or restart. It just dies instead. If it's quite difficult to get puppetmasterd to properly reload/restart on HUP, perhaps it would be easy enough to at least catch the signal and log that HUP is not supported? ---------------------------------------- Feature #2239: TERM signal should cause puppetd to exit as quickly as possible http://projects.reductivelabs.com/issues/2239 Author: Luke Kanies Status: Accepted Priority: High Assigned to: Luke Kanies Category: transactions Target version: 0.25.0 Complexity: Unknown Affected version: 0.24.8 Keywords: Currently, if puppetd receives either a TERM or an INT, it will finish its transaction before exiting. This can result in a too-long delay. Instead, one or both of these signals should cause Puppet to only finish the resource it's working on and then exit. -- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
