On Sun 26 Jul 2015 at 15:39:48 +0200, Vincent Lefevre wrote: > On 2015-07-26 14:25:20 +0100, Brian wrote: > > On Sun 26 Jul 2015 at 13:59:02 +0100, Lisi Reisz wrote: > > > On Sunday 26 July 2015 13:38:45 Michael Biebl wrote: > > > > > > > > Yes. You actually need to do that. As long as ntp is installed, > > > > systemd-timesyncd won't start. > > > > The assumption here is, that if the admin explicitly installed ntp, it > > > > should be preferred of systemd-timesyncd. > > > > See > > > > > > > > # > > > > /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.co > > > >nf [Unit] > > > > # don't run timesyncd if we have another NTP daemon installed > > > > ConditionFileIsExecutable=!/usr/sbin/ntpd > > > > ConditionFileIsExecutable=!/usr/sbin/openntpd > > > > ConditionFileIsExecutable=!/usr/sbin/chronyd > > > > > > So ntp won't actually harm anything. It is just unnecessary. > > > > It is necessary to purge it if you want to use systemd-timesyncd. If you > > prefer to use ntp instead of systemd-timesyncd it is not unnecessary. > > Can't the systemd configuration be changed without having to purge > ntp (e.g. to be able to switch between them easily)? > > IMHO, it is bad to be forced to uninstall a package just to make > some other package work.
Like not being able to have postfix/exim4 and cups/lprng on a machine at the same time, you mean? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/26072015144344.61e7b4816...@desktop.copernicus.demon.co.uk
