I wonder why don't they add a patch to NTP to do what Google/AWS does with
the leap second so we all don't have to face the problem.
On 20/05/2015 1:54 AM, Domen Kožar do...@dev.si wrote:
Yeah, leap second(s) are a big issue since that's the code that nobody
really tests. NixOS is going to have
Oh that looks useful. Perhaps I can set slew for all time, since I don't
expect my servers to ever be offline.
On 21/05/2015 1:13 AM, Domen Kožar wrote:
Running ntp with slew flag -x should give you same results as Google does.
To test a leap second before 30. June:
Running ntp with slew flag -x should give you same results as Google does.
To test a leap second before 30. June:
https://access.redhat.com/articles/199563
On Tue, May 19, 2015 at 5:56 PM, Roger Qiu roger@polycademy.com wrote:
I wonder why don't they add a patch to NTP to do what
Will NixOS be affected by the leap second issue that's coming up on June
30 2015?
--
Founder of Matrix AI
http://matrix.ai/
+61420925975
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
What is exactly the issue with this leap second, and what do you mean by
NixOS being affected?
On Tue, May 19, 2015, 11:56 Roger Qiu roger@polycademy.com wrote:
Will NixOS be affected by the leap second issue that's coming up on June
30 2015?
--
Founder of Matrix AI
http://matrix.ai/
Hi,
On 19/05/15 07:10, Roger Qiu wrote:
Will NixOS be affected by the leap second issue that's coming up on June
30 2015?
You shouldn't have issues if you're running ntpd.
--
Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/
___
nix-dev
http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-during-a-leap-second
On 19/05/2015 8:06 PM, Kirill Elagin kirela...@gmail.com wrote:
What is exactly the issue with this leap second, and what do you mean by
NixOS being affected?
On Tue, May
Yeah, leap second(s) are a big issue since that's the code that nobody
really tests. NixOS is going to have as much problems as the software
you're running has bugs.
Google is smart here, they're adding microseconds over a longer span of
time via their NTP, so the extra second doesn't disrupt any
