Le 16/04/2012 15:02, jcbollinger a écrit :
Moreover, I don't find the current behavior that bad. Is it better to
continue running the service with an out-of-date configuration? Is it
better to delay discovering the problem until the machine is
restarted, or until you or some other admin tries to restart the
service manually? If it were my server, the answers to both questions
would be "no".
I wholefully agree. My final objective is to test, reload is everything
is OK, and notifies otherwise so as to have the problem be corrected
ASAP. I described only initial step to make the point easier.
I don't want to interfere with native distribution initscripts, mainly
for maintenance reasons. However, using a custom wrapper could be the
solution here.
--
BOFH excuse #297:
Too many interrupts
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" 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-users?hl=en.
