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]"

Reply via email to