On Sat, Mar 12, 2011 at 11:14 AM, Ralph <ra...@depth.net> wrote: > Right. So what would be good is a solution along the lines of those methods > that simply use the time off the time servers without worrying about the local > clock, but that 'fix' the local clock in a more friendly way like ntpd does.
You may be missing the point. The point is that even in theory f the local clock jumps around and stops and starts you really can't measure its rate. What NTP does is measure the rate of the system clock and compare that rate to a set of reference clocks and then adjust the rate of the local clock to match the speed of the reference. If yu can't measure the local rate yu are not able to use this method. The best best is to "jump" the local clock when ever you notice there is some difference between it's time and the reference. So try this... run a script that pools a refference clock every minute or so. You can use "rtime" to get the time. subtract that from local time. If the difference is > 1 second reset the local time. This would fit in a small script of less then about 1 dozen lines. Use Bash shell, perl and whatever script you like. Might take 15 minute to set this up. -- ===== Chris Albertson Redondo Beach, California _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
