Jira (PUP-1054) Services should support 'reload' in addition to 'restart'

[Patrick Hemmer (JIRA)]

Title: Message Title

Patrick Hemmer commented on an issue   Re: Services should support 'reload' in addition to 'restart' I think the reason this becomes difficult is that now 'notify' and 'subscribe' become ambiguous. Do they reload, or to they restart? I think always doing one or the other is a bad idea. Sometimes you need both. Software upgrade needs a restart, but a config file change needs a reload. When the Package{} resource notifies, it should restart, when the File{} resource notifies, it should reload. I can only see one reasonable solution: Add subscribe_reload and notify_reload, along with a "reload" parameter to specify the reload command. This maintains backwards compatibility in that notify/subscribe will behave like they always did. The user can still override the restart command with the restart parameter. But now they have a separate reload if they want to use it. Add Comment   Puppet / PUP-1054 Services should support 'reload' in addition to 'restart' 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 ser... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.