-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Arnold Schekkerman wrote: > > My theory: a st1 may fluctuate due to load, temperature changes, signal > loss, etc. which is filtered by a st2. A st2 is less popular, so a well > configured st2 only fluctuates due to temperature changes. Therefore, it's > best to have a local time source or sync with st2 :-) >
Hmm.. never actually thought of it that way. I actually purposely wanted mine to be a st2 server because it would get more traffic than a st3. I figured I (read as: the company I work for) has a 10mbit connection at a highly secure datacenter and ntp traffic is so minimal in usage. So I'd make it a st2, kinda advertise it a bit (still haven't listed in the stratum 2 server list on ntp.org). And it was really stable for the longest time and then within the last couple weeks they've been varying wildly by a couple msec (heh, considering a couple msec to be "wild variance") when it always stayed within the +/- .5 msec range. - -- Todd http://www.vrillusions.com/ My PGP Key ID: 0xBC90230C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG8zJ6iSebwryQIwwRAseWAKC7g5xw7mvhEb/ypi7uFyJ8g+fm8ACfdVxk qr+tNTRmfHdN+mE3cyPoU50= =djgz -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
