On Jun 14, 2012, at 8:51 AM, David Schmitt wrote: > When something changes the service has to be notified. > When the service should not be restarted, puppet should not be running or the > Service%restart parameter should be set to /bin/true.
That's far too black/white for any real world scenario. Puppet not running just means it will catch it when it is, so that's not useful. And setting the restart parameter to bin/true would prevent content changes from restarting the process which defeats the purpose. You don't see any value in letting a service definition decide which things it cares to subscribe to -- like content, versus mode? -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
