[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ntp-bugs
Subject:    [ntp:bugs] [Bug 3613] New: 'pool' directive doesn't honor 'noselect' flag
From:       bugzilla-daemon () ntp ! org
Date:       2019-09-05 8:53:59
Message-ID: bug-3613-1197 () https ! bugs ! ntp ! org/
[Download RAW message or body]

https://bugs.ntp.org/show_bug.cgi?id=3613

             Bug #: 3613
           Summary: 'pool' directive doesn't honor 'noselect' flag
           Product: ntp
           Version: 4.2.8
          Platform: All
        OS/Version: All
            Status: CONFIRMED
          Severity: minor
          Priority: P5
         Component: ntpd
        AssignedTo: stenn@ntp.org
        ReportedBy: burnicki@ntp.org
                CC: bugs@ntp.org
    Classification: Unclassified


Martin Burnicki <burnicki@ntp.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |blocking4.2.8?

If I just want to monitor the accuracy I can get from some pool servers and add
the 'noselect' flag to the pool directive as in

pool pool.ntp.org iburst noselect

then the 'iburst' flag is honoured for pool servers that are added, but the
'noselect' flag is obviously ignored, so the pool servers are listed with a
tally code in the output of 'ntpq -p':


~ # ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*SHM(0)          .shm0.           0 l    6    8  377    0.000   -0.118   0.382
 pool.ntp.org    .POOL.          16 p    -   64    0    0.000    0.000   0.000
-time.convar.net 213.206.164.23   2 u   56   64  377   11.141  -21.799   3.106
-rondra.lf-net.o 130.149.17.21    2 u   57   64  377   10.820   -0.970   0.682
+stratum2-3.NTP. 129.70.130.71    2 u   51   64  377   17.327    1.431   0.725
-ns3.customer-re 237.17.204.95    2 u   53   64  377   16.754   -0.605   0.674
+tor-relais1.lin 193.79.237.14    2 u   49   64  377   10.762   -1.424   1.004

So the servers flagged with '+' also contribute to system time adjustments,
which is not desired in this case since it degrades the accuracy you can achive
with the SHM refclock alone.

Normal 'server' associations are never used to synchronize the system time if
marked with a 'noselect' flag.

-- 
Configure bugmail: https://bugs.ntp.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
bugs-announce mailing list
bugs-announce@lists.ntp.org
http://lists.ntp.org/listinfo/bugs-announce
[prev in list] [next in list] [prev in thread] [next in thread]