[Pacemaker] time synchronisation

[James Harper]

> 
> What is the behaviour of a cluster when the nodes are up to 10 minutes out
> of sync with each other, because they've just been booted up after a crash
> and the hwclocks are out of date and there is no ntp time source reachable?
> Could it cause lots of sig11's and constant re-elections because that's what I
> was seeing and it all seemed to go away once I artificially synchronised the
> clocks... I haven't tried to reproduce the problem so I can't be sure.
> 
> What is the best way on bootup in the above situation to ensure time
> synchronisation? Is it as simple as having a cron job to reset the hardware
> clock every so often so that on reboot things are reasonable?
> 

Also, could clock differences between nodes cause timeouts to be reported when there is no other evidence that a check timed out? I'm logging start and stop times for monitor events to a file and I'm seeing timeout errors even when there is always a stop logged for each start, and never more than a second between start and stop...

James