From owner-freebsd-current@FreeBSD.ORG Fri Feb 18 13:21:31 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B88016A4CE for ; Fri, 18 Feb 2005 13:21:31 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19BFA43D62 for ; Fri, 18 Feb 2005 13:21:31 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) j1IDLRkt061599; Fri, 18 Feb 2005 08:21:27 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)j1IDLRIr061596; Fri, 18 Feb 2005 08:21:27 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Fri, 18 Feb 2005 08:21:27 -0500 (EST) From: Andre Guibert de Bruet To: Doug White In-Reply-To: <20050217183425.O53092@carver.gumbysoft.com> Message-ID: <20050218081633.K637@alpha.siliconlandmark.com> References: <20050217140951.R637@alpha.siliconlandmark.com> <20050217183425.O53092@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: ntpdate behavior changes between 4.x, 5.x and CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 13:21:31 -0000 On Thu, 17 Feb 2005, Doug White wrote: > On Thu, 17 Feb 2005, Andre Guibert de Bruet wrote: > >> This is the output of ntpdate on a 4.11 machine: >> alpha# ntpdate -b time-b.nist.gov > /dev/null >> alpha# > > ntpd 4.1.0 > >> The following is output of ntpdate on a 5.3-stable machine: >> vnode# ntpdate -b time-b.nist.gov > /dev/null >> host found : time-b.nist.gov >> vnode# > > ntpd 4.1.1a > >> The following is the output of ntpdate on a CURRENT machine: >> bling# ntpdate -b time-b.nist.gov > /dev/null >> bling# > > ntpd 4.2.0 + patch to suppress those messages, which was obtained from the > upstream code. > > So the answer is "Because the vendor put it there, and we hid it again in > -CURRENT." Are there any plans to MFC ntpd 4.2.0? If adapting the patch for RELENG_5 (And 4.1.1a) would make the process any easier, could I get my mittens on it? Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >