RE: TIME loss
-Original Message- From: Peter A. Giessel [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 2:33 PM To: Jean-Paul Natola Cc: freebsd-questions@freebsd.org Subject: Re: TIME loss On 7/13/2006 10:13, Jean-Paul Natola seems to have typed: I do have the ntpd running, what does ntpq -p say? No association ID's returned ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: TIME loss
-Original Message- From: Peter A. Giessel [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 2:33 PM To: Jean-Paul Natola Cc: freebsd-questions@freebsd.org Subject: Re: TIME loss On 7/13/2006 10:13, Jean-Paul Natola seems to have typed: I do have the ntpd running, what does ntpq -p say? No association ID's returned ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Here's my rc.conf entry ntpdate_enable=YES ntpdate_program=ntpdate ntpdate_flags=-b 192.168.1.3 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TIME loss
IIRC, ntpdate only syncs your time at boot. You want something like ntpd_enable=YES On 7/13/06, Jean-Paul Natola [EMAIL PROTECTED] wrote: -Original Message- From: Peter A. Giessel [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 2:33 PM To: Jean-Paul Natola Cc: freebsd-questions@freebsd.org Subject: Re: TIME loss On 7/13/2006 10:13, Jean-Paul Natola seems to have typed: I do have the ntpd running, what does ntpq -p say? No association ID's returned ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Here's my rc.conf entry ntpdate_enable=YES ntpdate_program=ntpdate ntpdate_flags=-b 192.168.1.3 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: TIME loss
But as I mentioned earlier ntpd is running , when I do top -Original Message- From: Andy Greenwood [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 4:11 PM To: Jean-Paul Natola Cc: Peter A. Giessel; freebsd-questions@freebsd.org Subject: Re: TIME loss IIRC, ntpdate only syncs your time at boot. You want something like ntpd_enable=YES On 7/13/06, Jean-Paul Natola [EMAIL PROTECTED] wrote: -Original Message- From: Peter A. Giessel [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 2:33 PM To: Jean-Paul Natola Cc: freebsd-questions@freebsd.org Subject: Re: TIME loss On 7/13/2006 10:13, Jean-Paul Natola seems to have typed: I do have the ntpd running, what does ntpq -p say? No association ID's returned ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Here's my rc.conf entry ntpdate_enable=YES ntpdate_program=ntpdate ntpdate_flags=-b 192.168.1.3 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TIME loss
On 7/13/06, Jean-Paul Natola [EMAIL PROTECTED] wrote: Hi everyone, I have been trying to figure this one out for a couple of days, but no can do. My clock on my bsd box currently 19 minutes ahead of the real world. I have it set to query my w2k box as the time server. I do have the ntpd running, So I am not sure how to adjust I tried this milter# ntpdate -q 192.168.1.3 Looking for host 192.168.1.3 and service ntp host found : fci2003.fci server 192.168.1.3, stratum 2, offset -1120.152027, delay 0.03365 13 Jul 14:30:19 ntpdate[79951]: step time server 192.168.1.3 offset -1120.152027 sec But the longer the machine stays up (142 days ) the more time the clock loses, Aside from rebooting , is there any way to fix this? It doesn't really make sense to run ntpdate if ntpd is already running. ntpdate runs once, sets the clock, and then exists. ntpd runs continuously and keeps the clock synchronized to the server, but you must have the config file set up correctly. Do you have a line like server 192.168.1.3 in /etc/ntp.conf? You might also want to make sure rc.conf includes: ntpd_enable=YES ntpd_flags=-g -p /var/run/ntpd.pid The -g option lets it do a single large correction when it first starts, similar to ntpdate. If ntpd is running, then ntpq -p will tell you what peers it thinks it is trying to synchronize to, and what the status is. If it shows an asterisk (*) next to one of the peers, it is synchronized to that one. In your case, it will be a list of one. It takes a few minutes to synch after first starting up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: TIME loss
On Thu, 13 Jul 2006, Jean-Paul Natola wrote: But as I mentioned earlier ntpd is running , when I do top ...? Anyway, make sure your drift file exists and is writeable. Mine looks like this: $ ls -l /var/db/ntpd.drift -rw-r--r-- 1 root wheel 6 Jul 13 17:01 /var/db/ntpd.drift If it's not there, just # touch /var/db/ntpd.drift ...and verify permissions. ntpd should be able to take over from there. Another thing: (assuming you don't want to use ntpdate) ntpd may not sync to the time server if the local clock is very different from the server's clock. To sync the clock on boot, you can add ntpd_sync_on_start=NO # Sync time on ntpd startup, even if offset is high ...to /etc/rc.conf. HTH. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TIME loss
Jean-Paul Natola [EMAIL PROTECTED] wrote: But as I mentioned earlier ntpd is running , when I do top Couple of things: 1) NTP will refuse to adjust the clock if it's too far off. If your clock is drifting very badly, this may cause ntp to be unable to correct it. 2) If your clock is drifting as badly as you describe, you may benefit from switching to a different hardware clock. You can see which clocks are available via the sysctl kern.timecounter.choice, then trying changing kern.timecounter.hardware. 3) Check the logs for messages. Normal operation produces stuff like this: May 25 08:21:17 pa-plum1b-166 ntpd[130]: time set -32.027468 s May 25 09:04:19 pa-plum1b-166 ntpd[130]: time reset 0.758199 s 4) If the logs don't help, you can run ntpd in debugging mode with -d or -D level -Original Message- From: Andy Greenwood [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 4:11 PM To: Jean-Paul Natola Cc: Peter A. Giessel; freebsd-questions@freebsd.org Subject: Re: TIME loss IIRC, ntpdate only syncs your time at boot. You want something like ntpd_enable=YES On 7/13/06, Jean-Paul Natola [EMAIL PROTECTED] wrote: -Original Message- From: Peter A. Giessel [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 2:33 PM To: Jean-Paul Natola Cc: freebsd-questions@freebsd.org Subject: Re: TIME loss On 7/13/2006 10:13, Jean-Paul Natola seems to have typed: I do have the ntpd running, what does ntpq -p say? No association ID's returned ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Here's my rc.conf entry ntpdate_enable=YES ntpdate_program=ntpdate ntpdate_flags=-b 192.168.1.3 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bill Moran Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote. Benjamin Franklin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: TIME loss
On Thu, 2006-07-13 at 17:35 -0400, Chris Hill wrote: On Thu, 13 Jul 2006, Jean-Paul Natola wrote: But as I mentioned earlier ntpd is running , when I do top ...? Anyway, make sure your drift file exists and is writeable. Mine looks like this: $ ls -l /var/db/ntpd.drift -rw-r--r-- 1 root wheel 6 Jul 13 17:01 /var/db/ntpd.drift If it's not there, just # touch /var/db/ntpd.drift ...and verify permissions. ntpd should be able to take over from there. Another thing: (assuming you don't want to use ntpdate) ntpd may not sync to the time server if the local clock is very different from the server's clock. To sync the clock on boot, you can add ntpd_sync_on_start=NO # Sync time on ntpd startup, even if offset is high ...to /etc/rc.conf. HTH. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Wouldn't 'ntpd_sync_on_start=YES' work better? Or is it a very non-intuitive parameter? Refer to http://www.qnd-guides.org/qnd-ntpd.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: TIME loss
On Thu, 13 Jul 2006, Mike Jeays wrote: On Thu, 2006-07-13 at 17:35 -0400, Chris Hill wrote: [...] To sync the clock on boot, you can add ntpd_sync_on_start=NO # Sync time on ntpd startup, even if offset is high ...to /etc/rc.conf. Wouldn't 'ntpd_sync_on_start=YES' work better? Or is it a very non-intuitive parameter? Refer to http://www.qnd-guides.org/qnd-ntpd.html You're right, of course. I sit corrected. Maybe that's why my clock is wrong :^) Good link, BTW. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
