Issue #2239 has been updated by Ethan Rowe.
I'm not sure what the status of this is at present; I did a bunch of work reorganizing the process state management for this ticket, but it hasn't been committed. I couldn't quite get it stable by the 0.25 rc1 and we held off. Anyway, my work is here: http://github.com/ethanrowe/puppet/tree/tickets/master/2239 The coordination of stopping/restarting is clearer than what preceded it, but the exact behavior of the signal handlers is not quite what has been most recently discussed in this issue. If this work seems to be a decent approach for 0.26, I'm happy to tweak the signal handler methods and submit it for review. Just let me know what you think. Thanks. - Ethan ---------------------------------------- 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: Todd Zullinger Category: transactions Target version: 0.26.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 -~----------~----~----~----~------~----~------~--~---
