Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 May 2007 12:33:56 -0500
From:      Jeffrey Goldberg <jeffrey@goldmark.org>
To:        freebsd-stable@FreeBSD.ORG, Martin Dieringer <martin.dieringer@gmx.de>
Subject:   Re: clock problem
Message-ID:  <8EA8AB80-786A-431C-BFFD-6E244D3E25E8@goldmark.org>
In-Reply-To: <200705081429.l48ETYYr087578@lurza.secnetix.de>
References:  <200705081429.l48ETYYr087578@lurza.secnetix.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On May 8, 2007, at 9:29 AM, Oliver Fromme wrote:

> Martin Dieringer wrote:
>> Oliver Fromme wrote:
>>> Are you sure that your /etc/ntp.conf ist correct?
>>
>> # cat /etc/ntp.conf
>>
>> server time.fu-berlin.de iburst maxpoll 9
>> driftfile /var/db/ntp.drift
>> logfile /var/log/ntpd
>
> You must add "restrict" lines for every server and for
> localhost, like these:
>
> restrict time.fu-berlin.de nomodify
> restrict 127.0.0.1

Why?

That really makes no sense to me whatsoever.

> Other than that, the config looks good.  There's no need
> to add further time servers.

The time adjustment algorithms of NTP make use of multiple time  
sources.  NTP works best with having at least three reachable  
servers.  Of course ntp is designed to keep good time even when you  
are disconnected from the net, but it builds up its data from  
multiple sources and using triangulation to correct for errors.

Cheers,

-j


-- 
Jeffrey Goldberg                        http://www.goldmark.org/jeff/




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8EA8AB80-786A-431C-BFFD-6E244D3E25E8>