Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Aug 2015 15:40:25 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 202362] ntp: restore refclocks selection
Message-ID:  <bug-202362-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202362

            Bug ID: 202362
           Summary: ntp: restore refclocks selection
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: naddy@FreeBSD.org

Created attachment 159922
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=159922&action=edit
restore refclocks selection

The panicked update to ntp 4.2.8p1 in r280849 did not follow the configure
instructions in FREEBSD-upgrade. In particular, the selection of clock drivers
was not maintained and instead overwritten with the upstream defaults, enabling
numerous obscure drivers but disabling the comparatively popular RAWDCF
refclock.

To make matters more complicated, the previous clock selection in ntp/config.h
was already partially out of sync with FREEBSD-upgrade.

The attached patch restores the clock driver selection to that of r268351 and
updates the corresponding instructions in FREEBSD-upgrade.

A further discrepancy is --disable-debugging vs. #define DEBUG 1. The patch
does not address this.

This affects 11.0-CURRENT, 10.2-STABLE, and 10.2-RELEASE. I noticed the problem
when updating a box to 10.2R and ntpd only threw the cryptic error message
"PARSE receiver #0: parse_start: parse_setfmt() FAILED." instead of attaching
to my DCF77 time signal receiver.

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202362-8>