cyrus@convex.com (Tait Cyrus) (03/05/91)
Anyone have any suggestions/formulas on how to configure the 'fudge' line so that the time on a local machine matches 'real time'? I have a machine which I have configured as a stratum 4 machine timing off if it's own UN*X clock (we don't have NTP access to the Internet yet) and I want to set the 'fudge' line so xntp keeps time close to real time. My question is, is there a formula which I could to determine what value I should use for 'time1' given that I have access (only telnet) to a machine running xntp? At the present time I am running xclock on both machines and am setting the time by hand. I am also 'tweaking' the value for 'time1' every few days depending on the difference between local time and 'real time'. this 'tweaking' is getting REAL old REAL quick. It would be nice if I could get a diff between the local and remote machines, right now using date (yuck!), at two different times (now and a week from now) and then take the drift to figure out a "good" value for 'time1'. The doc doesn't really talk about values to set 'time1' to (maybe I just missed the forest for the trees). Any suggestions would be greatly appreciated. Thanks ___ W. Tait Cyrus Software Engineer Convex Computer Corporation cyrus@convex.com 2075 Research Parkway Suite B 719-594-4900 Colorado Springs, CO 80920 -- W. Tait Cyrus Software Engineer Convex Computer Corporation cyrus@convex.com 2075 Research Parkway Suite B 719-594-4900 Colorado Springs, CO 80920