3 ms·
It's probably just a patched NTP server that lies about current time.
by kccqzy 12y ago
It's probably just a patched NTP server that lies about current time.
- archimedespi 12y agoYou are exactly correct. The aforementioned thread[0] on Serverfault mentioned timesmearing with `ntpd -x`, as per [1]. It's a fairly well-known technique for avoiding some weird kernel-related bugs on leap seconds. [0]: http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-during-a-leap-second http://serverfault.com/questions/403732/anyone-else-experien... [1]: https://web.archive.org/web/20140221084401/http://my.opera.com/marcomarongiu/blog/2012/06/01/an-humble-attempt-to-work-around-the-leap-second https://web.archive.org/web/20140221084401/http://my.opera.c...