Peter Humphrey wrote:
On Saturday 08 January 2011 21:45:45 Dale wrote:

Now, with ntp, it logs to messages when it syncs, resets the clock
and such.  Does chrony do this somewhere too?  I have this in my
conf file:
[...]
logdir /var/log/chrony
You need to uncomment the next line too - the one that specifies what to
log. Remember that an exclamation mark is a comment marker in
chrony.conf.

Do I have to create a file for it to log to as well?
Nope. Just switch logging on, as above. If you have your syslog to
output to VT12 you can read its log output there. In my case I use
syslog-ng with the default config and VT12 switched on.

P. S.  I wonder why ntp and openntp didn't work?
Haven't a clue, but I do remember shuddering at the complexity of
configuring ntp, years ago. From reading this thread I get the impression
it hasn't improved much since then.

Here's my chrony.conf, minus comments; gate.ethnet is my gateway box:

server uk.pool.ntp.org
server gate.ethnet
maxupdateskew 10
driftfile /etc/chrony/chrony.drift
keyfile /etc/chrony/chrony.keys
commandkey 1
dumponexit
dumpdir /var/log/chrony
initstepslew 30 gate.ethnet
logdir /var/log/chrony
log measurements statistics tracking rtc
allow 192.168.2/24
allow 192.168.3/24
allow 192.168.4/24
logchange 0.5
cmdallow 127.0.0.1
rtcfile /etc/chrony/chrony.rtc
rtconutc

Incidentally, chronyd logs a "cannot open" error the first time it tries
to write to a log or dump file; it seems to be harmless.

HTH. I'm delighted you got something working!



I read the man pages and even used google but the part about what to log didn't register with me. Basically, I need to tell it where to put the log file, which I did, then what I want it to log as well, which I missed. Sort of like the way portage does in make.conf. I didn't catch what the last part meant. I added that to config and restarted it. Will see if that does what I want. I think it will.

I didn't have to much trouble with ntp the first time. I remember adding the servers to the conf file then doing some other little setting and just starting it as a service. After that, every once in a while I would update the servers. Some of them would drop off and have to many hops or something and just needed to be replaced. I don't recall ever having trouble like this before. Mostly the problems I did have was with the servers disappearing, moving or problems with network delays. It sure failed me this time tho. :-(

I'm going to try adding a line or two at a time until I get it set right then I'll post my config file in case someone else can use it as a reference.

Thanks for the help.

Dale

:-)  :-)

Reply via email to