I know, leap second preparedness is like sneeze preparedness to people
who have a life. But if you care about the pending hole in computers'
timeline, in about 2 minutes ntpd systems around the world will begin
announcing leap=01 instead of leap=00. If you are responsible for any
ntpd instances,
Robert Hegner wrote:
> I built NTP 4.2.7p285 ... Win7 ... public time servers.
> It works really bad. The offset jumps around like crazy
> and quite often it loses all its servers
> ...
> I'm not experienced with NTP so maybe it's just the
> configuration I use which is bad.
> ...
Make certain no
On Thu, Jun 28, 2012 at 11:53 UTC, Robert Hegner wrote:
> I built NTP 4.2.7p285 with Visual Studio 2010 and I'm trying to synchronize
> my Win7 box to some public time servers.
>
> It works really bad. The offset jumps around like crazy (-0.559s ... 0.174s)
> and quite often it loses all its server
Hi all
I built NTP 4.2.7p285 with Visual Studio 2010 and I'm trying to
synchronize my Win7 box to some public time servers.
It works really bad. The offset jumps around like crazy (-0.559s ...
0.174s) and quite often it loses all its servers (all entries are white
in NTP Time Server Monitor)
