-Original Message-
From: Sadique Urf Arbaz Sayyed
We started with a brand new windows server 2019 datacenter edition and
installed an infrastructure monitoring agent on it and strictly no other
program. The machine had 8 GB of memory. As part of monitoring NTP offset
from sync'd host we
On Wednesday, October 21, 2020 at 6:19:21 PM UTC+5:30, Jakob Bohm wrote:
> On 2020-10-21 12:45, Sadique Urf Arbaz Sayyed wrote:
> > On Wednesday, October 21, 2020 at 4:14:05 PM UTC+5:30, Sadique Urf Arbaz
> > Sayyed wrote:
> >> We started with a brand new windows server 2019 datacenter edition
On Wednesday, October 21, 2020 at 8:02:33 PM UTC+5:30, Jakob Bohm wrote:
> On 2020-10-21 15:16, Sadique Urf Arbaz Sayyed wrote:
> > On Wednesday, October 21, 2020 at 6:19:21 PM UTC+5:30, Jakob Bohm wrote:
> >> On 2020-10-21 12:45, Sadique Urf Arbaz Sayyed wrote:
> >>> On Wednesday, October 21,
We started with a brand new windows server 2019 datacenter edition and
installed an infrastructure monitoring agent on it and strictly no other
program. The machine had 8 GB of memory. As part of monitoring NTP offset from
sync'd host we scheduled a ntpqexe. The problem started after 4-5 days,
On Wednesday, October 21, 2020 at 4:14:05 PM UTC+5:30, Sadique Urf Arbaz Sayyed
wrote:
> We started with a brand new windows server 2019 datacenter edition and
> installed an infrastructure monitoring agent on it and strictly no other
> program. The machine had 8 GB of memory. As part of
Facebook is now using Chrony, you can read about their implementation:
Building a more accurate time service at Facebook scale
https://engineering.fb.com/production-engineering/ntp-service/
___
questions mailing list
questions@lists.ntp.org
