That's more of what we're looking to do. I think it would be a bad
idea to have puppet automatically updating clients. This would need
to be a one-off, scheduled item you would trigger from the puppet
master server, under the default {} node, I would presume;
Perhaps having the puppet (and facter) gem reside in a puppet://files/
URL and a definition within default {} that would ensure present and
latest (which could entail other dependencies like puppet.conf).
On Oct 8, 4:40 pm, Martin Langhoff <martin.langh...@gmail.com> wrote:
> On Fri, Oct 8, 2010 at 4:18 PM, Disconnect <dc.disconn...@gmail.com> wrote:
> > We just use packages:
> > package { "puppet": ensure => latest }
>
> If the rpm/deb script attempts to restart the service, that will stop
> puppet in the middle of the execution of the pkg manager itself.
> (Unless there's special handling of this case implemented somewhere in
> the toolchain -- see sshd).
>
> Seems safer to download the package file and schedule through
> something that decouples the pkg manager from the puppet client
> process.
>
> m
> --
> martin.langh...@gmail.com
> mar...@laptop.org -- School Server Architect
> - ask interesting questions
> - don't get distracted with shiny stuff - working code first
> -http://wiki.laptop.org/go/User:Martinlanghoff
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
