Here's the output:
systemctl cat ntpd.service # /usr/lib/systemd/system/ntpd.service [Unit] Description=Network Time Service Documentation=man:ntpd(8) Wants=network.target ConditionCapability=CAP_SYS_TIME After=network.target nss-lookup.target Conflicts=systemd-timesyncd.service
[Service] Type=forking PrivateTmp=true ExecStart=/usr/sbin/ntpd -g -N -u ntp:ntp # Specifying -g on the command line allows ntpd to make large adjustments to # the clock on boot. However, if Restart=yes is set, a malicious (or broken) # server could send the incorrect time, trip the panic threshold, and when # ntpd restarts, serve it the incorrect time (which would be accepted). Restart=no
[Install] WantedBy=multi-user.target [pgaltieri@truckin ~]$ systemctl status systemd-timesyncd.service ○ systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disable> Active: inactive (dead) Docs: man:systemd-timesyncd.service(8)
systemctl status systemd-timesyncd.service ○ systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disable> Active: inactive (dead) Docs: man:systemd-timesyncd.service(8)
Paolo
On 12/5/21 11:18, Francis.Montagnac@inria.fr wrote:
systemctl status systemd-timesyncd.service