Hello,
Thanks Peter for your reply.
On Tue, 17 Oct 2006, Peter A. Giessel wrote:
What does ntpq -p show?
$ ntpq -p
remote refid st t when poll reach delay offset
jitter
==
217.153.131.46
Hello,
On Tue, 17 Oct 2006, Chuck Swiger wrote:
Unless you've got additional restrict lines which permit some hosts to make
changes, using only restrict default ignore will prevent ntpd from paying
attention to the timeservers you've listed and it will even prevent ntpd from
changing the
Hello,
On Wed, 18 Oct 2006, Matthew Seaman wrote:
restrict default ignore
driftfile /var/db/ntp.drift
That means that anyone can connect to your NTP daemon and poll it for time
service or use ntpdc to muck around with your configuration. It's better
to use at minimum:
restrict default
Matthew Seaman wrote:
That means that anyone can connect to your NTP daemon and poll it for time
service or use ntpdc to muck around with your configuration. It's better
to use at minimum:
restrict default nopeer nomodify
restrict localhost
You *can* block that kind of unwanted
On Oct 17, 2006, at 10:51 PM, Matthew Seaman wrote:
This misconfiguration will also cause your ntpd to generate excessive
numbers of queries, rather than syncing up and reducing the NTP
polling
interval from minpoll to maxpoll. [1]
Remove that line and restart ntpd.
That means that anyone
Hello,
Sorry to bother again but I run ntpd on FBSD 6.1 and the clock differes by
about 30 seconds when I compare the time with top and this link
http://www.timeanddate.com/worldclock/city.html?n=262
My ntp.conf file looks like that:
server 2.pl.pool.ntp.org prefer
server
On 2006/10/17 14:13, Zbigniew Szalbot seems to have typed:
What am I doing wrong that instead of having the time synced I see more
and more discrepancy. When I rebooted and started the service 6 days ago
there was about 20 seconds difference. Now it is well over 30.
What does ntpq -p show?
On Oct 17, 2006, at 3:13 PM, Zbigniew Szalbot wrote:
My ntp.conf file looks like that:
server 2.pl.pool.ntp.org prefer
server 1.europe.pool.ntp.org
server 0.europe.pool.ntp.org
restrict default ignore
driftfile /var/db/ntp.drift
Unless you've got additional restrict lines which permit some
ntpd won't correct the clock if the difference is too large. So you need
to kill ntpd, run ntpdate to set the clock, then start ntpd up again.
-Derek
At 05:13 PM 10/17/2006, Zbigniew Szalbot wrote:
Hello,
Sorry to bother again but I run ntpd on FBSD 6.1 and the clock differes by
On Tuesday October 17, 2006 at 06:13:24 (PM) Zbigniew Szalbot wrote:
Sorry to bother again but I run ntpd on FBSD 6.1 and the clock differes by
about 30 seconds when I compare the time with top and this link
http://www.timeanddate.com/worldclock/city.html?n=262
My ntp.conf file looks like
On 2006/10/17 14:40, Derek Ragona seems to have typed:
ntpd won't correct the clock if the difference is too large. So you need
to kill ntpd, run ntpdate to set the clock, then start ntpd up again.
-Derek
At 05:13 PM 10/17/2006, Zbigniew Szalbot wrote:
ntpd_flags=-g -c
Chuck Swiger wrote:
On Oct 17, 2006, at 3:13 PM, Zbigniew Szalbot wrote:
My ntp.conf file looks like that:
server 2.pl.pool.ntp.org prefer
server 1.europe.pool.ntp.org
server 0.europe.pool.ntp.org
restrict default ignore
driftfile /var/db/ntp.drift
Unless you've got additional restrict
12 matches
Mail list logo
