[LEAPSECS] Windows 10 HOME leap second changes

[Tom Van Baak]

Good questions, and there are many more.

Maybe let's see if there's a way to contact the blog posters by email or phone. For something as important as true-UTC timekeeping on Windows, especially at the enterprise level, I'd expect to read formal technical specifications instead of a pair of folksy blog entries. It's hard to tell if this was intended as a comprehensive adoption of leap seconds for Microsoft products, or a one-time compliance check-list hack for certain high dollar customers. There are lots of red flags.

BTW, the TAI comment that you posted on the blog was fine; the reply was somewhere between defensive and wrong.

/tvb

----- Original Message ----- 
From: "GERRY ASHTON" <ashtongj at comcast.net>
To: "Leap Second Discussion List" <leapsecs at leapsecond.com>
Sent: Thursday, October 25, 2018 7:54 AM
Subject: [LEAPSECS] Windows 10 HOME leap second changes


> I was reading the two Microsoft blogs mentioned on the list in the last few days. The Windows time service seems to be w32tm. From the behavior of my laptop, I infer that this service is not normally running. I guess it is started when it's time to sync the clock to an NTP time server, and stopped when the syncing is finished. Does anyone know if that's true?
> 
> Does anyone know if the access to leap seconds by applications will be in home systems, or other systems that are not joined to a domain? (Not that I think such systems will have a serious need for such accuracy, but it might be interesting for tinkerers.)
> 
> Gerry Ashton
> _______________________________________________
> LEAPSECS mailing list
> LEAPSECS at leapsecond.com
> https://pairlist6.pair.net/mailman/listinfo/leapsecs