Checked my desktop's clock just now against Time.is
"Your time is exact!
The difference from Time.is was -0.003 seconds (±0.044 seconds)."
IIRC, I got a similar result the last time I tried this some months or
years ago.
I've been running Linux Mint 17.1 KDE64 for just over 3 years now so
have no idea of just how shite the MoBo's RTC actually is[1]. The quartz
crystal oscillators are stable enough, the problem is the manufacturers
simply can't be arsed to calibrate them[2].
The later versions of MS windows are pretty shoddy with regard to
syncing to NTP. That business of leaving the System Time to go unchecked/
corrected for a week at a time is yet one more minor (in the overall
scheme of MS badness) thing not to like about windows ten.
Just refreshed the page...
"Your time is exact!
The difference from Time.is was +0.001 seconds (±0.043 seconds)."
and a minute later...
"Your time is exact!
The difference from Time.is was +0.000 seconds (±0.044 seconds)."
That's via Opera's VPN. I'll turn off the VPN and try again.
"Your time is exact!
The difference from Time.is was +0.012 seconds (±0.026 seconds).
That's about what I'd expect having eliminated the extra latency of
Opera's VPN service. It also confirms that my 13 year old Casio Data Bank
360 watch is still one second ahead since the last time I had to rescue
it from January the first 2000[3] a week or so back.
Ever since I disabled the VPN option, subsequent refreshes with
time.is
have been giving differences in the +0.012 and +0.011 range (±0.025
seconds). The last time I checked the
time.is site under win2k, ISTR
seeing variations of 2 or 3 seconds between ntp sync events (but that was
with the previous MoBo which may or may not have had a less inaccurate
RTC).
=========================================================================
[NOTES]
[1] The OS upgrade from win2k to Linux Mint being the result of a major
hardware upgrade that had sidelined win2k (lack of driver support and
more importantly, the waste of a 64 bit CPU on a 32 bit OS).
The consequence being that I've been shielded from the RTC's
shortcomings as a cheap watch by Linux Mint's NTP daemon service which
not only takes care of syncing with ntp services, it also applies a
correction factor to the system clock to keep drift to a minimum, unlike
MS windows' system clock's time keeping.
With win2k at least, the user could choose their own internet time
synchronising schedule. AFAICR, I set mine on a 3 hour 59 minute schedule
to reduce clashes with requests from "The Whole World and their Dog" as a
compromise between overloading the servers and the clock error getting
out of hand.
I'd have to shut the PC down and unplug from the LAN, leave it say 12
hours and make sure to go straight into the cmos setup when I next power
up to see the RTC time before Linux gets its chance to 'correct the time'
using its calibrated correction factor when it's unable to access the
internet, if I want to see just how piss poor the RTC's accuracy is for
the lack of any attempt at calibration by the MoBo manufacturer.
[2] Not even to the humble timekeeping standards of your typical quartz
watch (a lousy +/- 30 seconds a month when, with a bit of care, they can
readily be set to stay within +/-1 second a month from one year's end to
the next before needing another tweak - assuming access to the padding
trimmer, not a normal option in the typical on-board RTC oscillator).
[3] It has the best thought out digital watch display I've *ever* seen
but after 9 years of faithful service, just as it had finally settled
down to an accuracy of +/- 1 second per annum, it took to blanking out/
resetting itself to the 1st of January 2000 every few months or so.
The last time I had to rescue it from its brief sojourn in the past, the
'shock' of the 'rescue' was so severe, the pin holding the retaining
toggle on the adjustable clasp of the stainless steel bracelet jumped
free. Luckily, I was able to find it and reassemble the clasp.
I really aught to replace it but the only digital watch that comes close
to the display ergonomics of my quirky Casio is another DB360 and the
only sensibly priced sources seem to be Ebay traders so I've played my
strong suite and procrastinated like crazy - it's what I do best.
--
Johnny B Good