On 05/02/2021 08:22, deloptes wrote: > basti wrote: > >> Hello, >> I use a up to date debian. As I can see now timedatectl seems *not* >> using the NTP Server provide by DHCP. I have configure a NTP server in >> LAN. >> >> timedatectl timesync-status >> Server: 167.86.86.192 (0.debian.pool.ntp.org) >> Poll interval: 1min 4s (min: 32s; max 34min 8s) >> Leap: normal >> Version: 4 >> Stratum: 2 >> Reference: CD2EB2A9 >> Precision: 1us (-24) >> Root distance: 45.645ms (max: 5s) >> Offset: +7.949ms >> Delay: 36.328ms >> Jitter: 0 >> Packet count: 1 >> Frequency: +79.117ppm >> >> >> ntpdate -bu raspi >> 4 Feb 22:15:53 ntpdate[21025]: step time server 192.168.30.5 offset >> -0.016785 sec >> >> Can someone confirm that? >> >> Best Regards > you are mixing up two different approaches. Try > > timedatectl show-timesync > > timedatectl has its config in /etc/systemd/timesyncd.conf > > ntpdate has no idea what systemd is doing > > set your NTP IP in /etc/systemd/timesyncd.conf > and restart And, for the D part in DHCP, the ArchWiki has as recipe for how to do this automatically using NetworkManager's dispatcher scripts. OP hasn't said what DHCP client they use, so some adaption might be required. > > systemctl restart systemd-timesyncd > > or disable the service > > systemctl status systemd-timesyncd > systemctl disable systemd-timesyncd > > Not so hard to read man pages though > > man timesyncd.conf > > regards > > >
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature