Is your clock in sync? (USA)

On 12/07/2020 21.37, Alan Baker wrote:
On 2020-07-11 4:42 p.m., Carlos E.R. wrote:
On 12/07/2020 01.35, Carlos E.R. wrote:
On 12/07/2020 00.22, Paul wrote:

...

Windows time synchronizes infrequently, and so an error
can accumulate between sync points. A period of a week
is selected, to avoid overloading timeservers. Timeservers
(should) have anti-hammering provisions - if you set the
sync interval to one minute, a good server will cut you off.
The pool.org server might not, because it's a pool and
has some form of load balancer. I don't personally
encourage the usage of pool.org . Use one of the government
ones, leave it set to a week etc.

Wow, one week. I must be spoiled by tools like ntpd in Linux, keeps
the clock accurate continuously within milliseconds using the pool.


I forgot. In a Windows Domain with Active Directory, keeping all the
machines in sync is crucial. A small error and you simply can not
login (Kerberos). It doesn't matter if the clock is correct, but all
the machines need have the same time.


It depends what you mean by "small error". It's been a while since I had
to work with an AD environment, but I believe you had to be about 5
minutes out for it to be a problem.

I don't remember that much, sorry.

--
Cheers, Carlos.