-------- In message <[email protected]>, Tony Finch writes:
>> The opererative detail is this: >> >> "Microsoft has determined that clocks on tens of thousands >> of servers globally running Azure should switch to the leap >> second at midnight in the time zone where they are based." >> >> As far as I know, it is not like Microsoft has any choice, "local >> midnight" is the only time their software makes it possible for >> them to make sure that all servers jump at the same time. > >But they have servers in multiple locations, so if they are running on the >local time zone they will not leap at the same time... Welcome to the (probably painful) world of "heuristic handling of leap seconds". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ LEAPSECS mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/leapsecs
