From: George Anzinger <george@mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux@horizon.com, linux-kernel@vger.kernel.org, johnstul@us.ibm.com
Subject: Re: NTP leap second question
Date: Fri, 16 Sep 2005 18:05:35 -0700 [thread overview]
Message-ID: <432B6BDF.2010607@mvista.com> (raw)
In-Reply-To: <1126920192.22339.7.camel@localhost.localdomain>
Alan Cox wrote:
> On Gwe, 2005-09-16 at 14:58 -0700, George Anzinger wrote:
>
>>What I am asking is when is the flag sent to the kernel. My reading of
>>the kernel code says that it will insert the second on the second roll
>>immeadiatly after the flag is set.
>
>
> Kernel clock ticks are not adjusted or slewed or anything else for a
> leap second when correctly configured. UTC leap second adjustment is
> performed by glibc for locales that expect it (which I think is all of
> them)
Eh?? Then what is one to make of the code in timer.c that add
leapseconds? It seems to be controlled by the adjtime() system call.
Sure looks like it sets the system clock (xtime) ahead or back by a
second at midnight if the flag is set to do so.
--
George Anzinger george@mvista.com
HRT (High-res-timers): http://sourceforge.net/projects/high-res-timers/
next prev parent reply other threads:[~2005-09-17 1:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 22:20 NTP leap second question linux
2005-09-16 21:58 ` George Anzinger
2005-09-17 1:23 ` Alan Cox
2005-09-17 1:05 ` George Anzinger [this message]
2005-09-17 1:53 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2005-09-14 17:48 [RFC][PATCH] NTP shift_right cleanup (v. A1) john stultz
2005-09-14 17:53 ` john stultz
2005-09-14 18:39 ` NTP leap second question George Anzinger
2005-09-14 18:54 ` john stultz
2005-09-15 6:49 ` Ulrich Windl
2005-09-15 17:21 ` Kyle Moffett
2005-09-15 18:35 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=432B6BDF.2010607@mvista.com \
--to=george@mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox