I''ll partially answer my own question... a script would be better than
chained execs. But I still think it would be handy to have a way to
"notify" services to start or stop rather than just restart.
I also think it would be handy to have a "precondition" parameter
which is like a notify, but before. For example:
file { "/etc/whatever":
precondition => Service["foo"](stop)
source => ...
notify => Service["foo"](start)
}
Or maybe "prenotify and postnotify" along with "presubscribe and
postsubscribe". You get the idea...
On Nov 13, 1:46 am, schickb <schi...@gmail.com>
wrote:> Several times I''ve found the need to perform a task while a
service
> was offline. For example, I wanted to replace the master "mysql"
> database for MySQL. The only way I''ve found to handle this
currently
> is with a cascade of "refreshonly" execs: The first exec takes
the
> service offline, second copies files (or whatever), third restarts the
> service.
>
> Is there a better way to handle this? Anyone else have this need?
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---