Heyho! On Sunday 04 April 2010 21.45:52 Dreamy wrote: > http://www.pool.ntp.org/scores/193.87.160.18/graph/offset.png > > I know it's still "fine", but I am curious if there is something > I can do with that (I want to have a REALLY stable time server).
As others have said: monitoring system hiccups. If you don't know the difference between sntp and "proper" ntp, now's the time to read up about it. If you want to monitor the performance of your timeserver, -> get it to output statistics and plot these (IIRC it was "loopstats" or something like it, long time since I've done this...) -> ideally, get a 2nd ntp (not sntp) machine (ideally on the same network, and the network should only be lightly used) and plot the offset that gives you. One easy "improvement", if you trust one of your timeservers to be very good most of the time, is to tell ntpd to prefer it as the primary time source. I've seen ntpd switch the primary time source regularly when there are several servers configured that are similarly good, which will result in the error estimation drifting around somewhat as ntpd's idea of the "correct" time changes. This improvement turns into a bad idea if the timesource you've told ntpd to prefer turns bad. (Is there an english word for the german "verschlimmbessern"?) Finally, you can always get a soldering iron and build your own stratum 1 clock from a GPS or long wave receiver. (I've done neither, but I'd probably do the long wave receiver, it's more fun since I can really "see" the full technology. GPS is easier and probably more reliable. So it depends what you want to get ... :-) cheers -- vbi -- featured link: http://www.pool.ntp.org
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
