David,
The problem is that they start in sync and over the course of a day drift
that far apart despite having NTP running. We're not sure why NTP isn't
correcting it along the way. Though at this point, we are looking at a
firmware bug.
Thanks!
Bob
===
Bob,
That is his point.
Initial time comes from MB clock.
System (OS) time is set from that at boot.
During NTP startup for a client it is normal to do a ntpdate to hard
set the OS clock (direct one time set).
From there ntpd would track and adjust.
HOWEVER, there are limits to how much ntpd will
On 10/05/2012 08:23 PM, Christopher Brown wrote:
That is his point.
Initial time comes from MB clock.
System (OS) time is set from that at boot.
During NTP startup for a client it is normal to do a ntpdate to hard
set the OS clock (direct one time set).
From there ntpd would track and
