Martin Gregorie  wrote:
> On Sun, 28 Jul 2019 00:26:47 +0200, Fokke Nauta wrote:
>
>> We have a local NTP time server on the server in our LAN. It get's the
>> time from some Dutch sites, and it spreads it around in our LAN. Should
>> I get the Pi to listen to this NTP server? If so, how would I do that?
>
> Everything you need is in one of these:
>
> man ntpd
> man 5 ntp.conf
>
> The first two deal with setting up ntpd. I install ntpd on my Linux
> systems as a matter of course with the instance on my house server set as
> the default time reference for the others, but my other  hosts also
> reference other time servers as well so there is no single point of
> failure.
>
> Or you can use ntpdate:
>
> man 8 ntpdate
>
> It is usually executed once at boot time but you could also run it every
> few hours or days by a cron job. However, but its manpage says it "has
> known bugs and deficiencies and nobody has volunteered to fix them in a
> long time. The good news is the functionality originally intended for
> this program is available in the ntpd and sntp programs",
>
> So look at the sntp manpage as well.

This is unusable information. Raspbian doesn't use ntp/ntpd since Debian
switched to systemd, it's not even installed. Details here, for instance:
https://wiki.archlinux.org/index.php/systemd-timesyncd
It should work out of the box: if the local dhcp server provides (an) ntp
server address(es), timesyncd will use it. Check which servers are used via
"timedatectl show-timesync --all"

--- SoupGate-Win32 v1.05