Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!lll-winken!uop!quack!mrapple From: mrapple@quack.sac.ca.us (Nick Sayer) Newsgroups: comp.protocols.time.ntp Subject: You're never going to believe this... Message-ID: Date: 1 Jun 91 05:27:11 GMT Organization: The Duck Pond, Stockton, CA Lines: 20 I have finally sat down for a day and managed to get the CHU driver's 'time2' fudge value set properly. The weird part? It's _NEGATIVE_! -0.05, to be precise. This is a Sun 3/160 running SunOS 4.1, with the recently-posted CHU kernel STREAMS module, and xntpd. I am doing a bad thing, perhaps, in that I am presuming that the utcclock program is correct. This especially with a trailblazer locked at 19200 baud dialing out at 1200 baud. Still, can anyone think of a good reason why the fudge time would be that wacky? BTW: fudge time1 is set to the propogation delay given by the propdelay program. -- Nick Sayer | Official Scapegoat for the | RIP: Mel Blanc mrapple@quack.sac.ca.us | MC68HC11 Mailing List. | 1908--1989 N6QQQ | To subscribe, send mail to | May he never 209-952-5347 (Telebit) | mc68hc11-request@quack.sac.ca.us | be silenced.