[ntp:questions] Leap second info in ntp-4.2.4p4

Mohan Kannekanti mkannekanti at edgewaternetworks.com
Tue Jun 2 18:58:47 UTC 2015

Hi Harlan,

Thanks for the information. I understand your points. I'm *only* trying 
to be get leap second fixes at the moment as we don't have much time to 
test the new ntpd feature across all our platforms.

Yes, I'm testing the kernels too.

Also, I'll definitely encourage our folks to be part of NTP Consortium.


On 06/02/2015 11:05 AM, Harlan Stenn wrote:
> Mohan Kannekanti writes:
>> Hi,
>> We are currently using ntpd version 4.2.4p4.
> Please see http://support.ntp.org/bin/view/Dev/ReleaseTimeline and
> understand your choice.
> You are running software that was released in December of 2006, and was
> EOL'd in December of 2009 with 4.2.6, which fixed between 630-1000
> issues.
> 4.2.6 was EOL'd in December of 2014 by the release of 4.2.8, which fixed
> over 1,100 issues.
>> As Leap second insertion is very close, we are trying to be safe from it.
>> here are few questions,
>> - Is 4.2.4p4 capable of receiving "Leap Second" information from NTP
>> servers??
> Yes.
>>    Below is our configuration.
>>    "server time.nist.gov  maxpoll  10  minpoll  6
>>     disable monitor
>>     restrict default noquery
>>     restrict -6 default noquery"
>> - Is there any way that I can test whether the current version is providing
>> of "Leap Second"??
>> - Are there any configuration changes required??
> Required, no.
> Useful, almost certainly.  For example, you could keep an updated
> leapseconds file on your server and refer to that in your config file.
> Have you tested your kernels to make sure they can handle a leap second?
> What about how your client machines will behave during the leap second?
>> - If our version is not good for handling leap second,
>>        1. What will be closest version to upgrade from 4.2.4p4.?? or
> Why would you *not* want to run the latest release of NTP?
>>        2. Any patches that we can apply to make 4.2.4p4 safe.??
> Perhaps, but you'd have to:
> - look at somewhere between 1,700 and 2,100 patches
> - decide which ones you wanted
> - apply and test the patches
> I'd also recommend your company (and EVERYBODY else who cares about
> network time) join the NTP Consortium at Network Time Foundation now:
>   http://nwtime.org/membership/why-join/
> The bind-9 tarball is about 8MB.  The ntp tarball is about 6.5MB.
> We don't have even 5% of the resources to develop and maintain NTP that
> ISC has to develop and maintain BIND.


This electronic message, including attachments, is intended only for the 
use of the individual or company named above or to which it is addressed. 
The information contained in this message shall be considered confidential 
and proprietary, and may include confidential work product. If you are not 
the intended recipient, please be aware that any unauthorized use, 
dissemination, distribution or copying of this message is strictly 
prohibited. If you have received this email in error, please notify the 
sender by replying to this message and deleting this email immediately.

More information about the questions mailing list