@toiletobserver
the effect of utc vs local time would always jump by your timezone offset to utc which is usually whole hours and some timezones have half or quarter hours or such, IMHO it shouldnt cause clock “drift”, that is unless thats a feature of windows time handling when the time has a huge offset.
ntpd used to slightly adjust the clock only if the offset to remote servers is something like few seconds and would “step” to immediately correct the system clock if its larger.
That’s interesting, i did notice the windows click went out of sync and didn’t understand why. Thanks
@toiletobserver
the effect of utc vs local time would always jump by your timezone offset to utc which is usually whole hours and some timezones have half or quarter hours or such, IMHO it shouldnt cause clock “drift”, that is unless thats a feature of windows time handling when the time has a huge offset.
ntpd used to slightly adjust the clock only if the offset to remote servers is something like few seconds and would “step” to immediately correct the system clock if its larger.