From: George Anzinger <george@mvista.com>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
yoshfuji@linux-ipv6.org, Roman Zippel <zippel@linux-m68k.org>,
Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>,
joe-lkml@rameria.de
Subject: NTP leap second question
Date: Wed, 14 Sep 2005 11:39:07 -0700 [thread overview]
Message-ID: <43286E4B.1070809@mvista.com> (raw)
In-Reply-To: <1126720398.3455.58.camel@cog.beaverton.ibm.com>
It appears that a leap second is scheduled. One of our customers is
concerened about his application around this. Could one of you NTP
wizards help me to understand NTP a bit better.
First, I wonder if we suppressed the leap second insert and time then
became out of sync by a second, would NTP "creap" the time back in sync
or would the one second out of sync cause it to quit?
Assuming NTP would do the "creap" thing, is there a way to tell NTP not
to insert the leap second?
--
George Anzinger george@mvista.com
HRT (High-res-timers): http://sourceforge.net/projects/high-res-timers/
next prev parent reply other threads:[~2005-09-14 18:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` George Anzinger [this message]
2005-09-14 18:54 ` NTP leap second question john stultz
2005-09-15 6:49 ` Ulrich Windl
2005-09-15 17:21 ` Kyle Moffett
2005-09-15 18:35 ` Alan Cox
2005-09-14 18:13 ` [RFC][PATCH] NTP shift_right cleanup (v. A1) Roman Zippel
2005-09-14 18:25 ` john stultz
2005-09-14 19:11 ` Roman Zippel
2005-09-14 18:40 ` [RFC][PATCH] NTP shift_right cleanup (v. A2) john stultz
2005-09-20 1:28 ` [PATCH] " john stultz
2005-09-21 3:24 ` [PATCH] NTP shift_right cleanup (v. A3) john stultz
2005-09-21 5:24 ` Nick Piggin
2005-09-21 8:13 ` Ulrich Windl
2005-09-21 12:18 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
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
2005-09-17 1:53 ` 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=43286E4B.1070809@mvista.com \
--to=george@mvista.com \
--cc=joe-lkml@rameria.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ulrich.windl@rz.uni-regensburg.de \
--cc=yoshfuji@linux-ipv6.org \
--cc=zippel@linux-m68k.org \
/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