On 2015-05-31 02:41 AM, Poul-Henning Kamp wrote:
--------
In message <556a6bd2.50...@edlmax.com>, Brooks Harris writes:
I can't find any authoritative announcement or statement to this effect
>from Microsoft, [...]
Please note that this is *only* about Microsofts Azure cloud service,
Yes, that's what that articles says, but what does Microsoft say?
(which according to rumours are mostly used to run Exchange servers).
Indeed, rumors. What does Microsoft say?
This is *NOT* how your private/work Windows machine will behave,
Well, that's my question. Sure, a single machine catches up when it
synchronizes to NTP. But what is Windows doing with the Leap Second
count in each timezone?
The article I referenced earlier said "Applies To:" various Windows
Server versions - it doesn't mention Vista, Win 7, Win 8, etc.
How the Windows Time Service Works
https://technet.microsoft.com/en-us/library/cc773013(v=ws.10).aspx
So, the timing mechanisms are complex, depending on Windows version,
hardware, and administration choices.
My question is, if Azure is doing this, what is Windows itself doing?
for that no new information is available and the most recent
guidance was that "somewhere between a second and an hour later
the clock will step a second".
"most recent guidance" from whom?
As I understand it, the clock would step a second when it syncs with
NTP, but note there are apparently different capability NTP clients in
various Windows versions. But what happens in different timezones?
-Brooks
_______________________________________________
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs
