Date: Thu, 13 Jul 2006 17:35:24 -0400 (EDT) From: Chris Hill <chris@monochrome.org> To: Jean-Paul Natola <jnatola@familycareintl.org> Cc: Andy Greenwood <greenwood.andy@gmail.com>, "Peter A. Giessel" <pgiessel@mac.com>, freebsd-questions@freebsd.org Subject: RE: TIME loss Message-ID: <20060713172641.Q43814@tripel.monochrome.org> In-Reply-To: <3A85D7EF44E1C744BF6434691F5659E997548B@www.fcimail.org> References: <3A85D7EF44E1C744BF6434691F5659E997548B@www.fcimail.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 chris@monochrome.org ** [ Busy Expunging <|> ]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060713172641.Q43814>