On 16 May 2011 21:05, Chris Phillips <[email protected]> wrote: > > > On 16 May 2011 20:14, Jonathan Gazeley <[email protected]>wrote: > >> Hi Chris, >> >> We have configured puppet to manage its own puppet.conf on clients, and to >> ensure that puppetd is running on all hosts. However it does not manage >> puppet.conf on the puppetmaster, so if we accidentally mess up the config, >> we won't break the puppetmaster. >> > > This seems a logical thing to do to me, I'll want to be able to turn on > archive_files sometimes, that's one angle I'm keen on. Would be useful to > separate the server and client config files though really, then it wouldn't > be irresponsible to manage the client side of the master server separately. > > Following on from this, if I do change puppet.conf and have a service subscription against it, should I be able to abort the rest of the run as puppet needs to reload? Or preferably restart and being the run again automatically? I'd like to ensure all clients report and all files are archived for a few months to be safe, and would like to be able to get this happening by pulling down the puppet.conf (so obviously not archive that specific file, but that's no problem) and restarting (or whatever is technically required to activate the changes. I see a restat become "scheduled" not actually restaring the service.
Thanks Chris -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.
