Date: Fri, 3 Dec 1999 16:55:57 -0600 From: "Mark Einreinhof" <montana1@home.com> To: "Sheldon Hearn" <sheldonh@uunet.co.za> Cc: "Freebsd-Questions" <freebsd-questions@FreeBSD.ORG> Subject: RE: XNTP help Message-ID: <000001bf3de1$8fb987e0$0201010a@cmr.net> In-Reply-To: <55351.944048305@axl.noc.iafrica.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tried what you said and it works initially, i.e. resyncs the time but still speeds up time as the days progresses. I think I may just take your lines below and create a script and run the script as a cron job. Any other thoughts? Should I add more than one server to ntp.conf? Cheers, -Mark -----Original Message----- From: Sheldon Hearn [mailto:sheldonh@axl.noc.iafrica.com]On Behalf Of Sheldon Hearn Sent: Wednesday, December 01, 1999 5:38 AM To: big-sky@altavista.net Cc: Greg Lehey; Freebsd-Questions Subject: Re: XNTP help On Wed, 01 Dec 1999 05:01:26 CST, "Mark Einreinhof" wrote: > I was hoping that if I waited a day, that FBSD would sync back up when > it does the daily security emails and such. Unfortunately that didn't > happen. As I write this the Win98 client shows 0459 CST and FBSD shows > 0703 CST. You'll probably find that xntpd is spotting such a large time difference that it thinks the remote server must be wrong. Do this as root: kill `cat /var/run/xntpd.pid` ntpdate tick.uh.edu xntpd -p /var/run/xntpd.pid This assumes that tick.uh.edu is the right time server to use. The ntpdate command will set the time correctly, whereafter xntpd should keep you in syunc. By the way, you should have told us that you were seeing these in /var/log/messages: time error -11886773 is way too large (set clock manually) :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000001bf3de1$8fb987e0$0201010a>