ntpdate behavior changes between 4.x, 5.x and CURRENT

[Andre Guibert de Bruet]

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/    >