< return to the brandensite

running commentary

The internet is filled with things. Here is one of them.

w32tm time resync doesn't always instantly resync 2023 Nov 20
In the "so nobody else struggles for an hour with this same stupid problem" department, I share this link to serverfault which explains that sometimes, in an Active Directory domain situation, w32time /rescync doesn't instantly resync time and that's by design. Not that it's noted by the application in anywhere obvious. As the Q&A explains: "If the local clock time of the client is less than three minutes ahead of the time on the server, W32Time will quarter or halve the clock frequency for long enough to bring the clocks into sync. If the client is less that 15 seconds ahead, it will halve the frequency; otherwise, it will quarter the frequency. The amount of time the clock spends running at an unusual frequency depends on the size of the offset that is being corrected." There's no official explanation as to why it does this, but the best guess is that this is to avoid disrupting software which expect time to flow in a linear manner and not jump around erratically.
< all running commentary