[comp.protocols.time.ntp] how to compensate master drift

bill@banana.fedex.com (bill daniels) (03/19/91)

NTP is probably overkill for my purposes but nonetheless I use it.  We poll
a reliable source from our NTP master once per day to set its clock.  The
resolution of the reliable source is 1 second.  Our master tends to get 
ahead of Mr. Reliable by about 1 second per day.  Is there a tuneable 
parameter some where, along the lines of ntpd.drift, for the master host?
I would like to be able to stabilize my local master so that it is less
likely to run ahead of the source clock.

bd
-- 
these ravings are in no way sanctioned by federal express corp
bill daniels			| voice:  (901)797-6328
federal express corp		| fax:    (901)797-6388
box 727-2891, memphis, tn 38194 | email:  bill@banana.fedex.com