----- Original Message -----
> From: "Axel Bock" <axel.b...@arbeitsagentur.de>
> To: puppet-users@googlegroups.com
> Sent: Wednesday, September 5, 2012 10:18:31 AM
> Subject: [Puppet Users] Re: notify vs. require of services
>
> hm, I still don't see the logic.
>
> I think this is a common scenario (please tell me I'm wrong) that you
> ensure presence of a service generally, and then deploy a config
> file, and on changes you want - of course - the service to be
> restarted. or ... not?!
why would you start a service before the config file is deployed?
surely you want to configure the service before starting it?
Puppet only manage any resource once during the process of applying
the catalog, so the common pattern is:
package{"something": ...}
file{"/etc/something/config": require => Package["something"], notify =>
Service["something"]}
service{"something":...}
this way it installs, then configures and then starts the service.
In future any change to the config file will restart the service.
--
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.
