Issue #1014 has been updated by Nigel Kersten. Status changed from Needs design decision to Accepted Assignee deleted (Nigel Kersten)
"if we want a reusable solution, I think it’s about ‘who’ and ‘how’ – who to notify, and how to notify them. " Absolutely. I don't want to keep hacking special cases up when we could solve them all by solving the "how" problem. ---------------------------------------- Feature #1014: Services should support 'reload' in addition to 'restart' https://projects.puppetlabs.com/issues/1014 Author: Adrian Bridgett Status: Accepted Priority: Normal Assignee: Category: service Target version: unplanned Patch: None Affected Puppet version: 0.24.7 Keywords: Branch: currently if a service needs kicking (e.g. a config file changed) you can notify the service, but this leads to a restart. It would be nice if a reload was done if the service was already running (although I suppose there are bound to be some services which require restarts for some files, reloads for others). A reload would be far faster (shorter service interruption) and potentially more robust. I'm looking at this since bind stop/start (I hadn't set "hasrestart") on Debian etch can fail - it looks like stop command doesn't wait for bind to exit (I'll raise a bug with Debian about that) -- 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.
