On Thursday, 8 March 2012 at 18:19, Dan White wrote: > Would it be overkill to be worried about launching the puppet agent before > the last run has finished ? > > If so, I would use a bash script that generates a pid-file like this: > http://www.xarg.org/2009/10/write-a-pid-file-in-bash/ > > That way, if the previous run is still running, you can skip doing it again > and probably send out a notification that there are serious problems causing > it to hang or run too long. > > “Sometimes I think the surest sign that intelligent life exists elsewhere in > the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > ----- Peter Berghold <salty.cowd...@gmail.com > (mailto:salty.cowd...@gmail.com)> wrote: > > > > If you are running out of cron you run the risk of multiple client systems > > accessing your puppet master all at once. This can become a scaling issue. > > My advice is to just execute "puppet agent" on bootup (or manually) on each > > machine and let them figure out when to talk to the master. >
I'm using such script to deal with this issue: #!/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin SLEEP=$(($RANDOM*1500/32767)) sleep $SLEEP puppetd -tv --report But puppet commander, about which Krzysztof mentioned seems to be better solution. I have switch to it scheduled in my todo list too. Best, -- Dominik Zyla -- 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.
