Following the instructions in Accurate System Time (NTP) -- Funtoo wiki page, I added chronyd to keep correct timing. However, the system's time isn't really following up real time. I guess it's chronyd (and me) to blame (?).
The interesting bits in /etc/chrony/chrony.conf are:
server ntp.otenet.gr #pinging it, it's alive maxupdateskew 100 driftfile /var/lib/chrony/drift keyfile /etc/chrony/chrony.keys commandkey 1 dumponexit dumpdir /var/lib/chrony initstepslew 10 ntp.otenet.gr logdir /var/log/chrony log measurements statistics tracking logchange 0.5 mailonchange nik@... # address erased rtcfile /etc/chrony/chrony.rtc rtconutc sched_priority 1 lock_all
Also, cat /etc/conf.d/chronyd
CFGFILE="/etc/chrony/chrony.conf" ARGS="" rc_need=dhcpcd
For completeness (dunno if really required), here is rc-status
Runlevel: default metalog [ started ] dhcpcd [ started ] chronyd [ started ] consolekit [ started ] fcron [ started ] lm_sensors [ started ] netmount [ started ] sshd [ started ] xdm [ started ] local [ started ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed xdm-setup [ started ] dbus [ started ] Dynamic Runlevel: manual
What can be done to get the system correct timing?
ps- is it really not possible to have an inline code tag here?
Last edited by Nikos Alexandris (2013-11-30 00:47:54)
Boom! I shuted down the machine and there were a couple of can't sync and can't stop messages referring to fcron, chronyd and hardware clock (if I remember correctly). I rebooted and (for) now it looks quite ok :-) I guess I did not properly restart chronyd after configuration changes?
For some reason my system's time-keeping isn't working as expected. The deviations are large -2 hours, for example after manually setting the time this morning. And this keeps "growing". Another problem is that I can't stop the service itself manually. In example, if I issue a stop, I get:
rc-service chronyd stop * Stopping chronyd ... * Failed to stop chronyd [ !! ] * ERROR: chronyd failed to stop
This looks "promising"... :-/
chronyc tracking 506 Cannot talk to daemon
How can I check that chronyd is
validly receiving information from the assigned servers not working?
How can I find out why rc-service stop doesn't do it's job?
Last edited by Nikos Alexandris (2013-09-20 14:19:04)
An old running "chronyd" was on the way, a strange one:
root 22155 0.0 0.0 13748 3516 ? SL Sep15 0:00 /usr/sbin/chronyd -f /etc/chrony/chrony.conf -s -r -s -r
What could have doubled the parameters? I manually added "-s -r" in the /etc/conf.d/chronyd file, in ARGS=. Are these provided elsewhere as well?
ps- It is funny that the BBCode help page contains inline text in "Mono" font but it is not possible to use it as inline [ code ] in this forum!
Last edited by Nikos Alexandris (2013-09-20 15:53:59)
Unfortunately, I've had some issues with chronyd again. I removed it and, at least, the clock works now ok. Need to investigate further why `chronyd` doesn't sync properly.