However, I'm getting the following error when starting sntp that I
wasn't before in rc.log:
* Setting clock via the NTP client 'sntp' ...
4 Jun 09:34:15 sntp[1626]: Started sntp
4 Jun 09:34:15 sntp[1626]: kod_init_kod_db(): Cannot open KoD db file
/var/db/ntp-kod
4 Jun 09:34:15 sntp[1626]: Error looking up (A) no: Name or service not
known
4 Jun 09:34:15 sntp[1626]: Error looking up (A) -r: Name or service not
known
2011-06-04 09:34:15.356315 (+0500) -0.010584 +/- 0.038147 secs
2011-06-04 09:34:15.403387 (+0500) -0.0013 +/- 0.000488 secs
2011-06-04 09:34:15.436536 (+0500) -0.006587 +/- 0.026062 secs
[ ok ]
Googling the first line of the error:
kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod
did come up with this 6 month old bug:
https://bugs.ntp.org/show_bug.cgi?id=1681
Is there something I need to do to fix this, or is this a
cosmetic/logging bug that will iron itself out with a later update?
Thanks guys (and gals)...
Using ntp-client here, works just fine.
--
caveat utilitor
♫ ❤ ♫ ❤ ♫ ❤ ♫ ❤
Hmmm... what runlevel do you have ntdp set to? Mine is 'default'...
Anyone? Did ntp/sntp change how it logs things? Or is this possibly due
to my /var partition not being mounted yet (its on an lvm partition)
when sntp tries to start?
It appears to be running, but like I said, I haven't seen anything in
the logs about a time sync event since I rebooted yesterday after
migrating to OpenRC:
myhost : Sat Jun 04, 10:53:24 : ~
# ps aux | grep ntp
root 457 0.0 0.0 8036 580 pts/3 R+ 10:53 0:00 grep
--colour=auto ntp
ntp 1802 0.0 0.0 36260 1600 ? Ss 09:34 0:00
/usr/sbin/ntpd -p /var/run/ntpd.pid -u ntp:ntp
myhost : Sat Jun 04, 10:53:54 : ~
#
myhost : Sat Jun 04, 15:18:57 : ~
# grep stratum /var/log/messages
myhost : Sun Jun 05, 11:04:24 : ~
#