[lkml]   [2005]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/13] Time: Reduced NTP Rework (part 2)
On 6 Dec 2005 at 12:26, George Anzinger wrote:

> > I think this is not a question at all whether people like leap seconds or not:
> > Either they want to have the current official time, or they do not. If they do
> > not, they won't care about NTP; if they do they'd use it.
> >
> > If they don't like leap seconds, they'd go into politics to forbid them by law.
> I don't think that is what happens now. Rather the leapsecond is not

Be aware of the following: If a recent NTP daemon detects an old NTP kernel
interface (like that of unpatched Linux), it will not use the NTP kernel interface
at all ("disable kernel"). Thus no leap second processing will happen (AFAIK).

> requested by ntp and either a) ntp sets the clock at the required time
> or b) it "creeps" it ahead or back by one second over a somewhat
> longer time. It is behavior b) that I have found some folks want. In
> no case do I see anyone wanting to drop the leapsecond, they just
> don't want the discontinuity it introduces and are willing to be a
> second (or if done properly, half a second) away from the correct time
> for a period of time around the official leapsecond.

Fight the real problem then: Update the kernel NTP interface to the current one
(which is several years old by now). It's named "nanokernel" by Dave Mills, and it
was exactly the reason why I had patched Linux 2.4 to provide a nanosecond clock
resolution (in theory), and I also thought that's the reason for having
nanoseconds with your patch set ;-)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-12-07 08:35    [W:0.063 / U:3.952 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site