On Saturday, April 28, 2012 2:11:23 AM UTC-7, Luke Bigum wrote:
>
> Yes, Puppet is perfect for your file-copy-and-hook scenario. In Puppet
> speak it's "notify" and "subscribe" between resources, here's a very
> quick example that will restart Some Daemon if /etc/resolv.conf
> changes:
>
> node 'somehost' {
> class { 'resolv': }
> }
>
> class resolv {
> $resolv_conf = '/etc/resolv.conf'
> $service_name = 'some-daemon'
>
> file { $resolv_conf:
> source => "puppet:///modules/${module_name}/${resolv_conf}",
> notify => Service[$service_name],
> }
>
....
But that requires the files be hosted on the puppet master.
What if the conf files are still rdisted out under /rdist/base instead?
What does that look like?
>Once
>you realise how easy it is to write modules you might be able to
> convince some of your admins to start packaging your code,
Sadly, the chances of getting all sysadmins to be dilligent about creating
packages are pretty much zero.
They only want to deal with premade downloadable packages.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/2xg3WgKnZN8J.
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.
