Hi Guys,
I''m just getting my head around Puppet. At the moment I''m
using Puppet to
manage an Apache config file across webservers on some test servers. I have
this all setup and am using Puppet to initiate a graceful Apache restart
after the file is updated from the Puppet Master.
What I''d like to do is force the clients to check in as soon as the
files
is changed rather than wait the default 30 minutes. I appreciate that I
could schedule a regular cron to start the client --onetime or increase the
client check-in time.
However, if I make a change to my httpd.conf file on the Puppet Master,
I''d
like to force the modified file to the clients in a staggered fashion
rather than wait for the clients to pick up the change.
I have looked at Mcollective but I"m not sure if there is an alternative
way just using Puppet?
I understand the default is for clients to pull config changes rather than
have them pushed from a master, but I really need to the ability to force a
client checkin rather than wait for it.
Thanks,
--
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/-/x6y-k4Muh6cJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.