On Fri, 22 Dec 2017 15:13:05 +0100 (CET)
"Carlos E. R."
On Friday, 2017-12-22 at 14:57 +0100, Peter Suetterlin wrote:
Carlos E. R. wrote:
On Friday, 2017-12-22 at 13:15 +0100, Peter Suetterlin wrote:
Hi,
While checking logs for some other stuff I stumbled across a line systemd-timesyncd[917]: Synchronized to time server 216.239.35.0:123 (time1.google.com).
WTF!?
What openSUSE release is this? In my Leap 42.2 I see no such thing.
Ah, Tumbleweed.
Yes, indeed. I also have a 42.2 machine (server), there it is also running as it should. And I'm very sure it had been running on the TW machine, too, at some point not too long ago.
I wonder if it might be related to whether I'm on wired or wifi network. Cannot check ATM, as I have no cable available.
I'm not even insisting on ntpd per se - it's more the doing-something-else-without-any-notice attitude of systemd. I'd definitely expect a notification that (and why) it isn't starting a demanded service.
Just disable systemd-timesyncd
Check its "vendor preset", maybe it is "enabled" now.
Your ntpd is not active. Mine is:
I know :p
But it is enabled, so it should have been started, no?
Yes, that is curious.
It seems to me that releasing code that ignores long-standing solutions to a difficult problem as part of a distro and going with a wild-assed proprietary (and INCOMPATIBLE) time source is grossly irresponsible. See https://www.theregister.co.uk/2016/12/02/google_public_ntp_servers/ and particularly the comments. As is often the case, El Reg has the skinny. So black marks to the openSUSE team for incorporating this part of systemd. Extremely black marks to the systemd team for implementing and shipping such a broken system. And of course may-the-devil-claim-them to the barstewards at google that came up with this unholy mess. What was it they said, 'Don't be evil' - hah! Roger Oberholtzer might want to be particularly careful about future upgrades. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org