Bug#805927: timesyncd does not automatically start after removing all NTP daemons
Josh Triplett
josh at joshtriplett.org
Tue Nov 24 05:53:31 GMT 2015
Package: systemd
Version: 228-2
Severity: wishlist
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
disables systemd-timesyncd if /usr/sbin/ntpd (or another NTP daemon)
exists. However, nothing causes systemd-timesyncd to automatically
start running after removing the last such daemon. Would you consider
adding such a mechanism? (For instance, you could add a trigger in
systemd that registers interest in the paths listed in
disable-with-time-daemon.conf.)
The reverse holds true as well: if you install such a daemon,
systemd-timesyncd does not automatically stop.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.3.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.113+nmu3
ii libacl1 2.2.52-2
ii libapparmor1 2.10-2+b1
ii libaudit1 1:2.4.4-4
ii libblkid1 2.27.1-1
ii libc6 2.19-22
ii libcap2 1:2.24-12
ii libcap2-bin 1:2.24-12
ii libcryptsetup4 2:1.6.6-5
ii libgcrypt20 1.6.4-3
ii libkmod2 21-1
ii liblzma5 5.1.1alpha+20120614-2.1
ii libmount1 2.27.1-1
ii libpam0g 1.1.8-3.1
ii libseccomp2 2.2.3-2
ii libselinux1 2.4-3
ii libsystemd0 228-2
ii mount 2.27.1-1
ii sysv-rc 2.88dsf-59.2
ii util-linux 2.27.1-1
Versions of packages systemd recommends:
ii dbus 1.10.4-1
ii libpam-systemd 228-2
Versions of packages systemd suggests:
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
ii udev 228-2
-- no debconf information
More information about the Pkg-systemd-maintainers
mailing list