“Systemd should not default to using time{1,2,3,4}.google.com”

Re:“Systemd should not default to using time{1,2,3,4}.google... by Sanddancer on Wednesday July 01, 2015 @02:29PM (#9814083)

So instead, he makes it google's problem. This is an even more unreasonable and irresponsible decision. If he doesn't feel his project has the manpower to handle support requests for default servers, then he shouldn't list any default servers.

[ Parent | on HN ]

Re:“Systemd should not default to using time{1,2,3,4}.google... by Merovius on Thursday July 02, 2015 @04:23AM (#9817506)

Lennart has stated very clearly, that if someone where to propose some other publicly available server, that he would be happy to put that down instead.

Also note, that the reporter didn't write "don't use this, we can't handle the load", but "don't use this, weird stuff will happen to your server".

But yes, I agree, Googles NTP servers should be removed as a default. But a vendor pool also isn't a solution apparently. Luckily, there are people actively working on a PR to simply have no default. So everyone should just calm down and give the issue a while to resolve itself, instead of venting here on HN.

[ Parent | on HN ]

Re:“Systemd should not default to using time{1,2,3,4}.google... by wang_li on Thursday July 02, 2015 @10:46AM (#9819205)

The reporting wrote, in his first paragraph:

>Google doesn't provide timeX.google.com as a public service.

That's the end of the conversation. How Google handles rare time events, whether it's reliable or scalable are all irrelevant.

[ Parent | on HN ]