Subject: Re: kern/24207: ntpd does not work properly on MP systems.
To: None <netbsd-bugs@netbsd.org>
From: Geoff Wing <mason@primenet.com.au>
List: netbsd-bugs
Date: 01/24/2004 08:21:04
christos@zoulas.com <christos@zoulas.com> typed:
: Look at the large offsets:
:      remote           local      st poll reach  delay   offset    disp
:      =======================================================================
:      =WWW.UREGINA.CA  166.84.149.248   2  512  377 0.11034  2.943641 0.00929
:      *nist1-ny.glasse 166.84.149.248   1  512  377 0.01353  3.121874 0.00735
:      =clepsydra.dec.c 166.84.149.248   1  512  377 0.09393  2.938217 0.00928
:      =otc1.psu.edu    166.84.149.248   1  512  377 0.02994  3.088238 0.00740
:      =louie.udel.edu  166.84.149.248   2  512  377 0.01747  3.273659 0.00734
:      =filbert.cc.colu 166.84.149.248   2  512  377 0.01768  3.113442 0.00739
:      =ntp2.usno.navy. 166.84.149.248   1  512  377 0.21408  2.968513 0.00928
:      =ftp.jensenresea 166.84.149.248   1  512  377 0.01797  2.939460 0.00928
:      =clock.isc.org   166.84.149.248   2  512  377 0.08876  3.105656 0.00735
:      =time.nrc.ca     166.84.149.248   2  512  377 0.05721  3.117920 0.00735
:      =seismo.cmr.gov  166.84.149.248   2  512  377 0.08006  3.257980 0.00737

Did you muck about with the refs?  Otherwise how is 166.84.149.248 at different
strata?  I have ntpd running on several i386 MP computers though the maximum
number of sources I'd have would be 5 or 6.

Regards,
-- 
Geoff Wing : <gcw@pobox.com>