Issue #2239 has been updated by Luke Kanies.
Todd Zullinger wrote: > Luke Kanies wrote: > > What should the behaviour be on HUP? Should we just ignore it, and force > > people to kill and restart? > > For 0.25.0, this would be the best thing it seems. Perhaps logging something > like: 'SIGHUP is currently unsupported, please restart puppetmasterd' ? That > way, it will at least be clear that puppet got the signal, which might cause > less admins to scratch their heads or file bugs. That seems perfectly reasonable - just have 'restart' do this instead of reexec'ing if we're the server. ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
