--- a/ntpd-r1.service	2019-10-26 20:09:36.000000000 +0200
+++ b/ntpd-r1.service	2020-01-13 14:02:13.215736680 +0100
@@ -2,14 +2,13 @@
 Description=Network Time Service
 After=network.target nss-lookup.target
 Conflicts=systemd-timesyncd.service
 
 [Service]
-Type=forking
+Type=simple
 PrivateTmp=true
-EnvironmentFile=-/etc/conf.d/ntp
-ExecStart=/usr/sbin/ntpd ${NTPD_OPTS}
+ExecStart=/usr/sbin/ntpd --configfile=/etc/ntp.conf --panicgate --user=ntp:ntp --nofork
 # 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