My biggest problems with ntpd are: 1) I have no idea whether it is actually working and doing its job, or failing for whatever reasons and 2) There is no way to force it to just "query the time now". Consequently, for now, I am switching from it to just running ntpdate from cron. I want to know if anyone has resolved these issues. Thanks i

On 2007-12-18, Douglas O'Neal <oneal@dbi.udel.edu> wrote: > Ignoramus28151 wrote: >> My biggest problems with ntpd are: >> >> 1) I have no idea whether it is actually working and doing its job, or >> failing for whatever reasons >> >> and >> >> 2) There is no way to force it to just "query the time now". >> >> Consequently, for now, I am switching from it to just running ntpdate >> from cron. >> >> I want to know if anyone has resolved these issues. >> >> >> Thanks >> >> i > > Issues resolved long ago. > 1. Read the log files. ntpd outputs information through syslog. If > what is says isn't enough, try adding a -d or two to the startup > command line. > 2. "query the time now" is something you generally want done only at > startup, which is when you run either ntpdate or ntpd -b. OK. I think that my problems stemmed from mentioning clock2.redhat.com in my ntp.conf. I went through a few servers and made sure that I either run ntpdate regularly, or else that ntpd is set up properly. i

Ignoramus28151 <ignoramus28151@NOSPAM.28151.invalid> writes: >My biggest problems with ntpd are: >1) I have no idea whether it is actually working and doing its job, or >failing for whatever reasons ntpq -p will show you what the last query of the verious clocks was. and will show you the offsets calculated for the various clocks. Note that ntp will not do better than about a few msec because of latencies in the networking software. >and >2) There is no way to force it to just "query the time now". Why do you want it to do that? You could use chrony which has a burst command to chronyc which queries the remote clocks now. But it is not clear what this will accomplish. Perhaps if you told us why you want these things, we could help you accomplish what you really want. If you really want accurate times, why not use the Garmin GPS18LVM to set up a microsecond accurate time standard on your machine? >Consequently, for now, I am switching from it to just running ntpdate >from cron. While possible, this does not adjust the rate of the clock to take out the worst discrepancies. Most computer clocks run from 10 to a hundred parts per million out in the rate of the cpu tick. That is seconds per day. ntp tries to adjust the clock rate so that the computer tick clock is accurate as well as the time being accurate. ntpdate simply adjusts the time itself AFAIK, and not the rate. >I want to know if anyone has resolved these issues. What issues? Neither of those sound like issues to me. >Thanks >i

["Followup-To:" header set to comp.os.linux.misc.] David Schwartz <davids@webmaster.com>: > > Can you be a bit more specific? What are you seeing? What are you > expecting to see? What is your configuration? What does 'ntpq -np' or > 'ntpdc -c sysinfo' show? I don't know about him, but here lots of interesting stuff, thanks. I didn't know about those before either. -- Any technology distinguishable from magic is insufficiently advanced. (*) http://blinkynet.net/comp/uip5.html Linux Counter #80292 - - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.