Anton Aylward wrote:

...

Telcontar:~ # systemctl status ntpd [...] └─3280 ntpd: asynchronous dns resolver ^^^^^^^^^^^^^^^^^^^^^^^^^ ????

I guess they fork a separate process for it. Maybe to not upset the time-keeping? -- Per Jessen, Zürich (4.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward wrote:

On 22/12/17 08:21 AM, Per Jessen wrote:

...

Anton Aylward wrote:

...

...

Telcontar:~ # systemctl status ntpd [...] └─3280 ntpd: asynchronous dns resolver ^^^^^^^^^^^^^^^^^^^^^^^^^ ????

I guess they fork a separate process for it. Maybe to not upset the time-keeping?

Curious. There is asynchronous DNS code for Ruby, Python and of course Perl as libraries.

Also for C etc - I use the "adns" library, it is really easy to work with.

I haven't looked at it. It does beg a question about how independent of the main system DNS resolver - dnsmasq in my case - it works.

As independent as any other app that does DNS lookups - it uses /etc/resolv.conf to find your DNS server, then just fires off multiple requests and processes the responses as they arrive. -- Per Jessen, Zürich (4.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: On Friday, 2017-12-22 at 14:30 +0100, Per Jessen 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.

And leap423.

I think it might be work in progress, it doesn't look complete:

- how do I configure it for multicast on IPv6 ? - authentication options? - is there an ntpq equivalent?

The program is there, just not configured to run: cer@Telcontar:~> locate timesyncd /etc/systemd/timesyncd.conf /usr/lib/systemd/systemd-timesyncd /usr/lib/systemd/system/systemd-timesyncd.service /usr/share/man/man5/timesyncd.conf.5.gz /usr/share/man/man5/timesyncd.conf.d.5.gz /usr/share/man/man8/systemd-timesyncd.8.gz /usr/share/man/man8/systemd-timesyncd.service.8.gz cer@Telcontar:~> cer@Telcontar:~> cat /etc/systemd/timesyncd.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See timesyncd.conf(5) for details. [Time] #NTP= #FallbackNTP=time1.google.com time2.google.com time3.google.com time4.google.com cer@Telcontar:~> Telcontar:~ # systemctl status systemd-timesyncd ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd-timesyncd.service(8) Telcontar:~ # Peter, do: systemctl disable systemd-timesyncd systemctl stop systemd-timesyncd systemctl enable ntpd systemctl start ntpd - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo9ES0ACgkQtTMYHG2NR9Vl/gCfQpkW11H0fn5D/4XfPuolL/8C CcoAnjJbImUugBZbMWHNR/D4xJz0XNa8 =QyQb -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo9EvEACgkQtTMYHG2NR9XBMACeIVL1MfpXt593lCAr3Uh5hoRC sYQAn213OC0ZIPcVih7pkPYFCXKKeWge =pCek -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2017-12-22 at 18:28 -0000, Dave Howorth wrote: ...

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.

+++------------ Google's also explained how its NTP servers will handle leap seconds, one of which will delay the arrival of 2017 by a second. “No commonly used operating system is able to handle a minute with 61 seconds,” Google says, so “Instead of adding a single extra second to the end of the day, we'll run the clocks 0.0014% slower across the ten hours before and ten hours after the leap second, and “smear” the extra second across these twenty hours. For timekeeping purposes, December 31 will seem like any other day.” But not if you use an NTP server that uses another method leap second handling. On the page for its time service, Google says “We recommend that you don’t configure Google Public NTP together with non-leap-smearing NTP servers.” - ------------++- Oh, my :-( Given that, I will never use time.google.com - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo9WJYACgkQtTMYHG2NR9XQTQCeK5y+FbTLCjSeY83aauIhF/fM BtgAn1eTyQhf19DFSLj+MbEFMXsAXnbx =Cpoh -----END PGP SIGNATURE-----

Op vrijdag 22 december 2017 19:28:20 CET schreef Dave Howorth:

On Fri, 22 Dec 2017 15:13:05 +0100 (CET)

"Carlos E. R." wrote:

...

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. Next time check your facts. Black marks for not doing so. Tumbleweed uses ntpd and nothing else. Neither does Leap.

-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

On Friday, 2017-12-22 at 14:57 +0100, Peter Suetterlin wrote:

...

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.

Indeed, it is. And what's even more mysterious (for me) is lrwxrwxrwx 1 root root 49 Aug 19 2016 /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service -> /usr/lib/systemd/system/systemd-timesyncd.service The link is not owned by any package, but the date is from the initial install of the system. And indeed, there it is, in /var/log/zypp/history: # 2016-08-19 18:53:21 ntp-4.2.8p8-24.1.x86_64.rpm installed ok # Additional rpm output: # Updating /etc/sysconfig/ntp... ..... # 2016-08-19 19:29:09 Output of systemd-presets-branding-openSUSE-0.3.0-26.1.noarch.rpm %posttrans script: ...... # Resetting systemd-timesyncd.service to the new default: enable # Created symlink from /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service to /usr/lib/systemd/system/systemd-timesyncd.service. So it would be interesting to know why yours is disabled then ;^> Ah no - on my server (Leap 42.2) it also is disabled, and the zypper log does not have a similar %posttrans line.... So there indeed it never got enabled. It also seems like the problem was only temporary: At least the current systemd-presets-branding-openSUSE in Tumbleweed (12.2-2.1) has no mention of timesyncd in its scripts (rpm -q --scripts systemd-presets-branding-openSUSE). My best guess at the moment would be that currently my network (wifi) only gets active once I log in, as this is handled by networkmanager, and ntpd waits for that to be started. Normally it would be starting directly during boot (eth0 is controlled by wickedd), before timesyncd. Now timesyncd is first (why does it not wait? Both have "After=network.target" in the service file), and ntpd has a conflict defined against timesyncd in ntpd.service and its start is silently dropped. I'll try that once I have wired network available again, but that is only next week. For sure the current setup is messy, and a trap for people relying on the traditional setup. But if it really had been only a temporary issue of the branding it might not even be worth writing a bug report.... Merry Xmas to all! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Michael Hirmke wrote:

Hi Peter,

have a look at /etc/systemd/timesyncd.conf.

Yes, had already done that. Once you *know* that some service is running ...

There you can configure your ntp servers. Besides that, you can switch off timeyncd or you can uninstall ntpd. For pure clients you no longer need ntpd, timesyncd is sufficient.

Yes, I might even switch to timesyncd, for my laptop that is indeed fine. The issue was more about how it had sneaked in (see my other answer to Carlos). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org