Il 19/11/18 01:18, Simon Lees ha scritto:
On 19/11/2018 00:21, Marco Calistri wrote:
Il 13/11/18 18:24, Achim Gratz ha scritto:
The handling of ntpd apparently switched from an old-style rc script to a systemd unit. Since then the stop script will take somewhere between ten seconds to a minute to declare success and continue with the shutdown. I don't see why it should take that long to shut down since ntpd really just closes the ntp logs and exits. The systemd unit file treats it as a forking daemon, which probably makes the check of whether the daemon has exited more involved. But ntpd can easily be told not to fork, so I think it should use the "-n" option in ExecStart and all the stuff that the current start script is doing should go into ExecStartPre?
Regards, Achim.
I was relying on ntpd service since ever until I read about "chronyd" as the substitute of ntpd adopted by new opensuse releases, then I switched to chronyd.
Despite this it seems ntp package being still necessary (?) or could be removed by the system?
It shouldn't be necessary into the future, there have been a couple of issues making that happen but hopefully it will be done soon if not now.
I had removed (zypper rm) ntpd some weeks ago but it went installed again at first zypper dup. Also would like to report a known *bug* or perhaps a not expected behaviour of chronyd about wrong permission warning on /var/run/chrony: sudo systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor pre> Active: active (running) since Mon 2018-11-19 09:03:20 -02; 4min 32s ago Docs: man:chronyd(8) man:chrony.conf(5) Process: 1405 ExecStartPost=/usr/share/chrony-helper update-daemon (code=exit> Process: 1067 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUC> Main PID: 1103 (chronyd) Tasks: 1 (limit: 4592) Memory: 1.2M CGroup: /system.slice/chronyd.service └─1103 /usr/sbin/chronyd nov 19 09:03:12 linux-turion64 systemd[1]: Starting NTP client/server... nov 19 09:03:13 linux-turion64 chronyd[1103]: chronyd version 3.4 starting (+CM> nov 19 09:03:13 linux-turion64 chronyd[1103]: Wrong permissions on /var/run/chr> nov 19 09:03:13 linux-turion64 chronyd[1103]: Disabled command socket /var/run/> nov 19 09:03:13 linux-turion64 chronyd[1103]: Frequency -12.652 +/- 26.222 ppm > nov 19 09:03:20 linux-turion64 systemd[1]: Started NTP client/server. It has been reported also for other distros, I mean it is not a specific opensuse's chrony error. In addition I also would like to ask about the second warning: "Disabled command socket /var/run/" is it an error we can correct in some way or it is just an informative message? Thanks and regards, -- Marco Calistri Build: openSUSE Tumbleweed 20181116 Kernel: 4.19.1-1-default - Cinnamon 3.8.9