This site is not affiliated with Linus Torvalds or The Open Group in any way. Re: NTP driftfile donikatz Oct 19, 2006 11:55 AM (in response to boydd) ah, the default conf file. no_sys_peer seems entirely normal though it sounds bad. man ntpd mentions a different drift file /etc/ntp.drift which doesn't seem to exist. this contact form
A simple "ntpd -q -g" will work, but only if you have neither orphan mode, or the local clock reference defined in your config file. From experience, I've found using the undisciplined local clock reference causes problems with the initial 'large' adjustment ntpd does on startup. Your server settings in /etc/ntp.conf file should look like this, with the exception that you change the "0.us.pool.ntp.org" to "0.ca.pool.ntp.org:" Code:
The last message in /v/l/m about ntp is from the restart: Dec 7 14:38:32 firewall ntpd: peers refreshed Dec 7 14:38:32 firewall ntpd: Listening on routing socket on fd #26 for from 10.2.4.30, though it is ok from the other. This is a fake driver intended for backup # and when no outside source of synchronized time is available. Put this in a directory which the daemon can write to. # No symbolic links allowed, either, since the daemon updates the file # by creating a temporary in the same
I've resorted to using the old style ntp.conf format (That took care of the problem).DB Like Show 0 Likes (0) Actions 5. Anyway, that's why I now recommend removing the local clock reference these days, though if your clock is always reasonably in-sync you're never likely to see this behaviour anyway. I think this may be because I created an empty file. If the old settings are lost, I'm not sure how a full reinstall would help.
epia# ls -al /var/db/ntpd.drift -rw-r--r-- 1 root wheel 6 Jul 14 14:05 /var/db/ntpd.drift epia# cat /var/db/ntpd.drift 0.000 . . . In case the local host is # controlled by some external source, such as an external oscillator or # another protocol, the prefer keyword would cause the local host to # On our 2.5.1 and 2.5.3 boxes, the /etc/ntp was properly owned by "ntp" user by default.The KB should be adjusted to reflect this discrepancy. It was 10 fast last night.
Re: NTP driftfile jlanders Oct 20, 2006 7:52 PM (in response to donikatz) That's frustrating.Can you run 'ps -auxwww' and verify that you're running ntpd as user 'ntp'(the left most column by the way, it wrote a drift file as soon as I started the daemon.That sounds like a permissions issue to me...I think I have mine currently set up at /etc/ntp.drift Posts: 383 Rep: Have you made sure you've upgraded the ntp? How did the Romans wish good birthday?
Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the but I have no ideas why I'm getting the other errors. Get your hardware clock set to UTC. If you'd like to contribute content, let us know.
up vote 3 down vote favorite 1 It seems that CentOS does not have a ntp.drift or similar file. weblink The -g argument to ntpd will allow the time to be set to any value without restriction, so Bad Things Can Happen if the CMOS battery is dead (imagine all your The figures for delay and jitter are abnormally high. You do not need to fiddle with anything else in the stock file.
Physically locating the server How to handle a senior developer diva who seems unaware that his skills are obsolete? Ntp doesn't seem to be updating this file anymore, and I have verified it's ntp:ntp 644. Seriously, take the orphan thing out of your /etc/ntp.conf and make it look like this: Code:
Re: NTP driftfile boydd Oct 19, 2006 12:08 PM (in response to jlanders) Joe - I had opened an SR quite a while ago (SR 266819) - KB was supposed to
Find More Posts by irgunII 04-30-2014, 08:25 AM #11 tronayne Senior Member Registered: Oct 2003 Location: Northeastern Michigan, where Carhartt is a Designer Label Distribution: Slackware 32- & 64-bit and errors Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Hi all, Following the suggestions regarding setting timekeeping up as a daemon I did and errors Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the freebsd-questions mailing list [RndTbl] system loses time Trevor Cordes yet.
This takes about 15 minutes, when ntpd begins to continuously track timing and frequency changes, relative to the current server. Still no drift file, even though ntpq shows the ntpd running.sigh. I was speaking from my own personal experience. his comment is here Any help greatly appreciated.
I agree that it creates the file immediately, but did it actually put a drift value in the file right away? After an hour or so, ntpd writes the frequency drift factor to the configured drift file, which is then used at subsequent starts to allow ntpd to immediately enter its normal Thus, an adjustment as much as 600 s will take almost 14 days to complete. NTP has finer grained control than that, so we look at errors of margin using 0.0001% (0.000001, or 1 PPM).
That is not an NTP issue, NTP is just the unfortunate victim. See the tinker configuration file directive for other options. disable monitor # # Trust ourselves. :-) restrict 127.0.0.1 restrict ::1 If you edit the server section to Code: # # NTP server (list one or more) to synchronize with: #server If you need to reset your password, click here.
Either way, NTP will synchronize time for you. I have *always* used local time since the gmt thing only confuses me or I forget that I'm on it and think I've screwed something up by seeing the time and WilliamS View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by WilliamS 04-29-2014, 11:41 PM #9 WilliamS Member Registered: Nov 2003 Location: 46N Thanks JoeDoug: Apologies for not using your pasted config exactly, although I suppose my mistake made the exact cause leap out.
Since the server line does not have the prefer keyword, this driver # is never used for synchronization, unless no other other # synchronization source is available. Thus: 1 PPM = 1 part per million = 1 microsecond per second = 3.6ms per hour = 86.4ms per day Thus, my drift file shows the value of "2.643" which Was this the complete output? If you remove the NTP drift file altogether, it will take longer for ntpd to figure out the drift rate and therefore write the drift file.
I'm currently using openntp. "I know nothing except the fact of my ignorance."- Socrates Offline #7 2006-11-25 15:31:41 Convergence Member Registered: 2005-07-02 Posts: 370 Re: ntp.drift is always empty (SOLVED) I The man page doesn't explain what units are being used for the drift.