-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Oct 12, 2005, at 0:22 , Adrian von Bidder wrote:
Just curious: what kind of software does 85.196.2.102 run? Server is
detected as falseticker here (offset > 150ms, jitter >10ms and varying
wildly where the other server all have single-digit figures) and
doesn't
respond to ntpq -p requests.
(Yes, the server is still fine to run ntpdate against, but I don't
know if
an ntp is able to sync against it even if it's the only server.)
<http://www.pool.ntp.org/scores?ip=85.196.2.102> is not that
pretty, either.
As you said, it's fine for ntpdate. However with the pool being the
default ntpd configuration I've been pondering lowering the "maximum
offset considered OK" value a bit again so the servers will be more
likely to be okay for ntpd as well. What I had in mind was catching
edge cases like this. I'm tempted to change the algorithm[1] so a
server will slowly drop out of the offset is more than say 150 or
200ms (right now it's 500ms).
As a random example another server in Greece has a much better
offset; so I'm reasonably confident that it won't punish an otherwise
good server: http://www.pool.ntp.org/scores?ip=212.251.14.84
- ask
[1] my $recv_org = $pkt{'Receive Timestamp'} - $time_now;
my $trans_dest = $pkt{'Transmit Timestamp'} -
$time_then;
$offset = abs(($recv_org + $trans_dest) / 2);
if ($offset > 3 or $pkt{Stratum} > 5) {
$step = -4;
}
elsif ($offset > 1.5) {
$step = -2;
}
elsif ($offset > 0.1) {
$step = -2 * $offset + 1;
}
else {
$step = 1;
}
}
- --
http://www.askbjoernhansen.com/
-----BEGIN PGP SIGNATURE-----
iQCVAwUBQ07Hq/koKP1ixIspAQKLlAP+NF3SwboDrRG5VRXtlR/uj441zXJMdAqN
Awoov0xIywHP0fF9ZUuocMXepizEgacGZlzg7ngNYifLTY23thVC/PYc5iEDBPVZ
tZcRDxSZw7RJXGdVMiDVOPX6Y2kKZaBJWcBGVDXtNVq8GBFLGwQ0prjy8bnts4Iz
LyZ79+n1/eg=
=yCtF
-----END PGP SIGNATURE-----
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
