If you look at /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
# don't run timesyncd if we have another NTP daemon installed *ConditionFileIsExecutable=!/usr/sbin/ntpd* ConditionFileIsExecutable=!/usr/sbin/openntpd ConditionFileIsExecutable=!/usr/sbin/chronyd ConditionFileIsExecutable=!/usr/sbin/VBoxService So it's completely disabled with NTP On Sunday, February 10, 2019 at 11:05:40 AM UTC-8, vince wrote: > > On Sunday, February 10, 2019 at 10:44:48 AM UTC-8, V. Kelly Bellis wrote: >> >> http://weewx.com/docs/usersguide.htm states that I should run a NTP >> <http://www.ntp.org/> daemon, but doesn't address an existing/ running >> pre-installed timesync service; e.g., installed with Raspbian via NOOBS >> >> Elsewhere <http://raspberrypi.tomasgreno.cz/ntp-client-and-server.html>, >> we read that timesync and NTP should not be run at the same time - "*but >> you can not have running both of them at the same time*" >> >> Is the pre-installed timesync sufficient for weewx? Either way, could the >> users guide include some mention of timesync's shortcomings or sufficiency >> insofar as weewx is concerned? >> >> >> > The users guide can't/shouldn't try to cover all the nuances of every > operating system nor the sheer unfettered joy that is systemd (ha - beat > Matthew to it!) > > What happens is if you run NTP, systemd gets out of the way and doesn't > enable its ntp hack/feature/whatever. > > So, FWIW, I always run NTP because I have decades of positive experience > with that software. It's a well-understood thing. Much easier to debug > when that's needed. > > (and any time I can disable systemd 'helping' me, I tend to do so. That > thing is much harder to debug when it goes whacko.) > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
