-----BEGIN PGP SIGNED MESSAGE-----
I am probably missing something, but can't you just ignore the leap second
until you discover that the time is 1 sec off and then use the normal NTP
procedure to get back to the exact time
On Tue, 8 Sep 1998, Andrej Presern wrote:
> Date: Tue, 8 Sep 1998 22:27:28 +0200
> From: Andrej Presern <[email protected]>
> To: [email protected],
Ulrich Windl <[email protected]>
> Cc: [email protected]
> Subject: Re: GPS Leap Second Scheduled!
> On Mon, 07 Sep 1998, Ulrich Windl wrote:
> >(...About leap second handling in the Linux kernel...)
> >On 1 Sep 98, at 11:16, Sven Dietrich wrote:
> >> The GPS control segment has posted a leap second warning for week number
> >> 990, Day number 5, and thus it's official in GPS world,
> >> that the leap second will take place 12/31/98...
> >> I am going to run simulations on NTP 3 & 4 and Linux with that GPS almanac.
> >> Will send bug fixes and patches as needed for the Trimble refclocks and
> >> NTP...
> >> Linux currently inserts a 2nd 59th second, instead of the UTC model of ...
> >> 58, 59, 60...
> >The time in the kernel is seconds since the epoch. To insert a second
> >means that we'll have to delay the next second for another second.
> >The other solution seems to be a clib -> kernel interface that knows
> >that a leap second is active now. Then the clib could possibly
> >convert the seconds to xx:yy:60. (I hope I did not overlook something
> Have you considered simply not scheduling any processes for one second and
> adjusting the time accordingly? (if one second chunk is too big, you can do it
> in several steps)
> Andrej Presern, [email protected]
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> Please read the FAQ at http://www.tux.org/lkml/faq.html
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
-----END PGP SIGNATURE-----