On Jun 11, 2009, at 5:52 PM, Pete Emerson wrote:
> Hrm, I'm running it with --foreground so that I know when it's
> complete, and I'm getting these execution expired messages, which I
> took to mean that puppetrun already has some sort of internal
> timeout mechanism. Is that not the case?
>
> I guess an alternative would be to run with --no-foreground. If I do
> that, is there a way to query host and see when it's last successful
> update was, in order to show that the changes have been completed?
>
> If that doesn't work, then I guess I'd have to ssh to each box and
> run puppetd there and wait for it to finish.
I'd recommend using reports from the client to figure out when it's
done.
--
The truth is that there is nothing noble in being superior to somebody
else. The only real nobility is in being superior to your former self.
-- Whitney Young
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
