I have a very simple-minded puppet.pp class, displayed in full at the bottom.

When I update the file source of the puppet.conf file, the file gets
distributed to the slave systems, but the service does not then get
restarted.  The doc says the service gets restarted whenever it receives "
an event"; isn't updating a file in the class an event?

I manually restarted the puppet service on one of the clients, and then
the new config file immediately took effect.

So what am I overlooking?

(By the way, the lock file issue I asked about previously seems to have
cleared itself up with a couple of restarts; that is, it went away while I
was thrashing on other things.)

Here's the puppet class, as promised:

# $Id: puppet.pp 549 2008-11-26 16:30:47Z David.Dyer-Bennet $

# This is amusingly, or perhaps recursively, warped.  We want to
# deploy a stock puppet config, so that the server name gets
# distributed during bootstrapping.

class puppet {
    file { "/etc/puppet/puppet.conf":
        owner => root,
        group => root,
        mode => 644,
        source => "puppet:/files/lserver/puppet.conf"
    }
    file { "/etc/puppet/namespaceauth.conf":
        owner => root,
        group => root,
        mode => 644,
        source => "puppet:/files/lserver/namespaceauth.conf"
    }
    package { "puppet":
        ensure => latest,
    }
    service { "puppet":
        ensure => running,
        enable => true,
    }
}



-- 
David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to