Laurens2000
Grote kans dat de file chrony.conf leeg is, dat gebeurd wanneer je tijdens het rooten de stroom er te snel af haalt en de file inhoud nog in het geheugen zit
even inloggen en hem vullen met:
`server 0.nl.pool.ntp.org minpoll 8
server 1.nl.pool.ntp.org minpoll 8
server 2.nl.pool.ntp.org minpoll 8
server 3.nl.pool.ntp.org minpoll 8
#keyfile /etc/chrony/chrony.keys
#commandkey 1
driftfile /var/lib/chrony/chrony.drift
#log tracking measurements statistics
logdir /var/log/chrony
dumponexit
dumpdir /var/lib/chrony
local stratum 10
we're not a server
#allow 192.168/16
Generate syslog messages if large offsets occur (> x secs)
logchange 10
Specify that the real time clock keeps UTC not local time
rtconutc
#rtcfile /var/lib/chrony/chrony.rtc
Step system clock if large correction is needed (> x secs within y clkupdates)
makestep 1000 100
Trim the system clock on boot-up. (> x secs from host)
initstepslew 30 0.nl.pool.ntp.org
initstepslew 30 1.nl.pool.ntp.org
initstepslew 30 2.nl.pool.ntp.org
initstepslew 30 3.nl.pool.ntp.org
Stop bad estimates upsetting machine clock
maxupdateskew 100.0
only allow chrony access locally``