Excuse the pseudo-code, but could you pipe the "ntpdate" command to "at now +5
minutes"? It'll exit with status 0, allowing puppet to go in its merry way, and
the time will sync up "soon", hopefully before puppet runs again.
If you could force the module to run very late in the chain, you could
On Wed, Dec 14, 2011 at 16:00, Corey Osman wrote:
> I have the following manifest that basically syncs the time for nodes really
> out of sync and ntpd can't drift the time back fast enough.
>
> The problem is that when puppet executes the catalog, and puppet changes the
> time, puppet never f
Hi,
I have the following manifest that basically syncs the time for nodes really
out of sync and ntpd can't drift the time back fast enough.
The problem is that when puppet executes the catalog, and puppet changes the
time, puppet never finishes because it can't calculate the "run time" since
