[ntp:bugs] [Bug 435] If refclock local is fudged to stratum 0 the refid is always INIT

[bugzilla at ntp.isc.org]

http://bugs.ntp.isc.org/show_bug.cgi?id=435





------- Additional Comments From mills at udel.edu  2005-05-24 13:52 -------
Subject: New: If refclock local is fudged to stratum 0 the
 refid is always INIT

Martin,

Setting the local clock driver stratum to zero is not supported. There 
is no useful reason to do this.

Dave

bugzilla at ntp.isc.org wrote:

>http://bugs.ntp.isc.org/show_bug.cgi?id=435
>
>           Summary: If refclock local is fudged to stratum 0 the refid is
>                    always INIT
>           Product: ntp
>           Version: dev
>          Platform: Other
>        OS/Version: Linux
>            Status: NEW
>          Severity: normal
>          Priority: P3
>         Component: ntpd
>        AssignedTo: stenn at ntp.org
>        ReportedBy: martin.burnicki at meinberg.de
>                CC: bugs at ntp.isc.org,mills at udel.edu
>
>
>I know that fudging the local clock to stratum 0 is normally not advisable. 
> 
>However, under some conditions it is useful. If the local clock local is fudged 
>to stratum 0 then the refid is initialized to "INIT" and it always stays at 
>this state (displayed in the "ntpq -p" billboard. 
> 
>This is not good since INIT normally is set for reference time sources 
>(servers) that have not been reached. 
> 
>Best regards, 
> 
>Martin
>
>
>
>------- You are receiving this mail because: -------
>You are on the CC list for the bug, or are watching someone who is.
>





------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.