Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #100032 > unrolled thread

'Leap Second' to Be Added on New Year's Eve This Year

Back to article view | Back to comp.lang.c

Contents

  'Leap Second' to Be Added on New Year's Eve This Year "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2016-12-22 21:43 +0800
    Re: 'Leap Second' to Be Added on New Year's Eve This Year Siri Cruise <chine.bleu@yahoo.com> - 2016-12-22 05:48 -0800
      Re: 'Leap Second' to Be Added on New Year's Eve This Year "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2016-12-22 22:09 +0800
      Re: 'Leap Second' to Be Added on New Year's Eve This Year Krzysztof Mitko <invalid@kmitko.at.list.dot.pl> - 2016-12-24 13:47 +0100
        Re: 'Leap Second' to Be Added on New Year's Eve This Year Siri Cruise <chine.bleu@yahoo.com> - 2016-12-24 05:39 -0800
    Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2016-12-22 14:31 -0600
      Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Storkamp <mstorkamp@yahoo.com> - 2016-12-23 08:34 -0600
        Re: 'Leap Second' to Be Added on New Year's Eve This Year "J-P. Rosen" <rosen@adalog.fr> - 2016-12-23 16:55 +0100
        Re: 'Leap Second' to Be Added on New Year's Eve This Year Ken Brody <kenbrody@spamcop.net> - 2016-12-30 11:17 -0500
          Re: 'Leap Second' to Be Added on New Year's Eve This Year Gene Wirchenko <genew@telus.net> - 2016-12-30 09:38 -0800
            Re: 'Leap Second' to Be Added on New Year's Eve This Year hah <hah@no.email.stupid.invalid> - 2016-12-30 15:59 -0600
          Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2016-12-30 15:47 -0600
          Re: 'Leap Second' to Be Added on New Year's Eve This Year Ken Blake <Ken@invalid.news.com> - 2016-12-30 15:14 -0700
            Re: 'Leap Second' to Be Added on New Year's Eve This Year Kaz Kylheku <221-501-9011@kylheku.com> - 2016-12-30 23:26 +0000
      Re: 'Leap Second' to Be Added on New Year's Eve This Year "James R. Kuyper" <jameskuyper@verizon.net> - 2017-01-03 20:46 -0500
    Re: 'Leap Second' to Be Added on New Year's Eve This Year Jason <jason_warren@ieee.DELETE.org> - 2016-12-22 17:14 -0500
      Re: 'Leap Second' to Be Added on New Year's Eve This Year "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2016-12-22 14:38 -0800
      Re: 'Leap Second' to Be Added on New Year's Eve This Year "Jonathan N. Little" <lws4art@gmail.com> - 2016-12-22 17:40 -0500
        Re: 'Leap Second' to Be Added on New Year's Eve This Year Jason <jason_warren@ieee.org> - 2016-12-23 19:57 -0500
          Re: 'Leap Second' to Be Added on New Year's Eve This Year Char Jackson <none@none.invalid> - 2016-12-23 21:44 -0600
            Re: 'Leap Second' to Be Added on New Year's Eve This Year "James Wilkinson Sword" <imvalid@somewear.com> - 2016-12-31 23:42 +0000
      Re: 'Leap Second' to Be Added on New Year's Eve This Year Ken Brody <kenbrody@spamcop.net> - 2016-12-30 11:16 -0500
        Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2016-12-30 15:58 -0600
          Re: 'Leap Second' to Be Added on New Year's Eve This Year Keith Thompson <kst-u@mib.org> - 2016-12-30 14:37 -0800
            Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2016-12-30 19:16 -0600
              Re: 'Leap Second' to Be Added on New Year's Eve This Year Keith Thompson <kst-u@mib.org> - 2016-12-30 17:48 -0800
                Re: 'Leap Second' to Be Added on New Year's Eve This Year Jorgen Grahn <grahn+nntp@snipabacken.se> - 2016-12-31 10:08 +0000
                Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2016-12-31 14:20 -0600
                Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2016-12-31 14:34 -0600
                  Re: 'Leap Second' to Be Added on New Year's Eve This Year Wally W. <ww84wa@aim.com> - 2016-12-31 16:45 -0500
                    Re: 'Leap Second' to Be Added on New Year's Eve This Year Ken Blake <Ken@invalid.news.com> - 2016-12-31 16:34 -0700
                      Re: 'Leap Second' to Be Added on New Year's Eve This Year "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2016-12-31 17:15 -0800
                      Re: 'Leap Second' to Be Added on New Year's Eve This Year Wally W. <ww84wa@aim.com> - 2016-12-31 20:52 -0500
                      Re: 'Leap Second' to Be Added on New Year's Eve This Year Richard Heathfield <rjh@cpax.org.uk> - 2017-01-01 12:22 +0000
                      Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2017-01-01 15:47 -0600
                  Re: 'Leap Second' to Be Added on New Year's Eve This Year Keith Thompson <kst-u@mib.org> - 2016-12-31 13:59 -0800
                Re: 'Leap Second' to Be Added on New Year's Eve This Year Wally W. <ww84wa@aim.com> - 2017-01-01 13:46 -0500
                  Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2017-01-01 16:12 -0600
                    Re: 'Leap Second' to Be Added on New Year's Eve This Year Wally W. <ww84wa@aim.com> - 2017-01-01 19:44 -0500
                      Re: 'Leap Second' to Be Added on New Year's Eve This Year Wally W. <ww84wa@aim.com> - 2017-01-01 22:31 -0500
                    Re: 'Leap Second' to Be Added on New Year's Eve This Year Ken Blake <Ken@invalid.news.com> - 2017-01-02 11:23 -0700
                      Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2017-01-02 19:03 -0600
                    Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Storkamp <mstorkamp@yahoo.com> - 2017-01-02 13:46 -0600
                      Re: 'Leap Second' to Be Added on New Year's Eve This Year Wolf K <wolfmac@sympatico.ca> - 2017-01-02 14:55 -0500
                        Re: 'Leap Second' to Be Added on New Year's Eve This Year Andy Burns <usenet@andyburns.uk> - 2017-01-02 20:00 +0000
                          Re: 'Leap Second' to Be Added on New Year's Eve This Year Sam E <why.should.this@be.email.invalid> - 2017-01-02 19:07 -0600
                            Re: 'Leap Second' to Be Added on New Year's Eve This Year Gareth Owen <gwowen@gmail.com> - 2017-01-03 06:45 +0000
                              Re: 'Leap Second' to Be Added on New Year's Eve This Year Wolf K <wolfmac@sympatico.ca> - 2017-01-03 09:42 -0500
                              Re: 'Leap Second' to Be Added on New Year's Eve This Year "Cybe R. Wizard" <cybe_r_wizard@WizardsTower.invalid> - 2017-01-03 11:27 -0600
                                Re: 'Leap Second' to Be Added on New Year's Eve This Year Caver1 <caver1@inthemud.org> - 2017-01-03 14:25 -0500
                              Re: 'Leap Second' to Be Added on New Year's Eve This Year "James R. Kuyper" <jameskuyper@verizon.net> - 2017-01-03 17:34 -0500
                        Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Storkamp <mstorkamp@yahoo.com> - 2017-01-02 14:20 -0600
                          Re: 'Leap Second' to Be Added on New Year's Eve This Year Wolf K <wolfmac@sympatico.ca> - 2017-01-02 15:36 -0500
                          Re: 'Leap Second' to Be Added on New Year's Eve This Year "James R. Kuyper" <jameskuyper@verizon.net> - 2017-01-04 12:09 -0500
                            Re: 'Leap Second' to Be Added on New Year's Eve This Year Wolf K <wolfmac@sympatico.ca> - 2017-01-04 19:12 -0500
                      Re: 'Leap Second' to Be Added on New Year's Eve This Year Wally W. <ww84wa@aim.com> - 2017-01-02 15:06 -0500
                        Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2017-01-02 19:10 -0600
                          Re: 'Leap Second' to Be Added on New Year's Eve This Year Wally W. <ww84wa@aim.com> - 2017-01-02 22:56 -0500
                        Re: 'Leap Second' to Be Added on New Year's Eve This Year "James R. Kuyper" <jameskuyper@verizon.net> - 2017-01-04 12:34 -0500
                          Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2017-01-04 15:32 -0600
                            Re: 'Leap Second' to Be Added on New Year's Eve This Year Keith Thompson <kst-u@mib.org> - 2017-01-04 13:51 -0800
                              Re: 'Leap Second' to Be Added on New Year's Eve This Year Real Troll <real.troll@trolls.com> - 2017-01-04 19:02 -0400
                              Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2017-01-04 22:37 -0600
                            Re: 'Leap Second' to Be Added on New Year's Eve This Year "James R. Kuyper" <jameskuyper@verizon.net> - 2017-01-04 17:21 -0500
                              Re: 'Leap Second' to Be Added on New Year's Eve This Year "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-04 16:35 -0800
                                Re: 'Leap Second' to Be Added on New Year's Eve This Year asetofsymbols@gmail.com - 2017-01-06 01:53 -0800
                                  Re: 'Leap Second' to Be Added on New Year's Eve This Year asetofsymbols@gmail.com - 2017-01-06 01:58 -0800
                            Re: 'Leap Second' to Be Added on New Year's Eve This Year Gene Wirchenko <genew@telus.net> - 2017-01-05 09:20 -0800
                              Re: 'Leap Second' to Be Added on New Year's Eve This Year "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-01-05 10:23 -0800
                              [OT] Meaning and truth (Was Re: 'Leap Second' to Be Added on New Year's Eve This Year) Wolf K <wolfmac@sympatico.ca> - 2017-01-05 13:34 -0500
                            Re: 'Leap Second' to Be Added on New Year's Eve This Year Caver1 <caver1@inthemud.org> - 2017-01-07 17:20 -0500
                              Re: 'Leap Second' to Be Added on New Year's Eve This Year Kaz Kylheku <221-501-9011@kylheku.com> - 2017-01-07 22:57 +0000
                                Re: 'Leap Second' to Be Added on New Year's Eve This Year "James R. Kuyper" <jameskuyper@verizon.net> - 2017-01-07 19:06 -0500
                                  Re: 'Leap Second' to Be Added on New Year's Eve This Year Kaz Kylheku <221-501-9011@kylheku.com> - 2017-01-08 06:16 +0000
                                    Re: 'Leap Second' to Be Added on New Year's Eve This Year "James R. Kuyper" <jameskuyper@verizon.net> - 2017-01-08 11:19 -0500
                      Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2017-01-02 19:05 -0600
                      Re: 'Leap Second' to Be Added on New Year's Eve This Year "James Wilkinson Sword" <imvalid@somewear.com> - 2017-01-04 00:28 +0000
              Re: 'Leap Second' to Be Added on New Year's Eve This Year raltbos@xs4all.nl (Richard Bos) - 2017-01-01 10:01 +0000
            Re: 'Leap Second' to Be Added on New Year's Eve This Year Mark Lloyd <not@mail.invalid> - 2016-12-31 14:29 -0600
    Re: 'Leap Second' to Be Added on New Year's Eve This Year "James Wilkinson Sword" <imvalid@somewear.com> - 2016-12-31 21:57 +0000
      Re: 'Leap Second' to Be Added on New Year's Eve This Year "James R. Kuyper" <jameskuyper@verizon.net> - 2017-01-03 20:06 -0500
        Re: 'Leap Second' to Be Added on New Year's Eve This Year "James Wilkinson Sword" <imvalid@somewear.com> - 2017-01-04 15:44 +0000
          Re: 'Leap Second' to Be Added on New Year's Eve This Year "James R. Kuyper" <jameskuyper@verizon.net> - 2017-01-04 14:11 -0500
            Re: 'Leap Second' to Be Added on New Year's Eve This Year "James Wilkinson Sword" <imvalid@somewear.com> - 2017-01-04 19:58 +0000
        Re: 'Leap Second' to Be Added on New Year's Eve This Year Richard Heathfield <rjh@cpax.org.uk> - 2017-01-04 16:17 +0000
          Re: 'Leap Second' to Be Added on New Year's Eve This Year "James Wilkinson Sword" <imvalid@somewear.com> - 2017-01-04 21:03 +0000
            Re: 'Leap Second' to Be Added on New Year's Eve This Year "Osmium" <r124c4u102@comcast.net> - 2017-01-05 14:15 -0600
              Re: 'Leap Second' to Be Added on New Year's Eve This Year "James Wilkinson Sword" <imvalid@somewear.com> - 2017-01-06 01:26 +0000
        Re: 'Leap Second' to Be Added on New Year's Eve This Year antispam@math.uni.wroc.pl - 2017-01-05 19:28 +0000
          Re: 'Leap Second' to Be Added on New Year's Eve This Year "James Wilkinson Sword" <imvalid@somewear.com> - 2017-01-05 21:41 +0000
    Re: 'Leap Second' to Be Added on New Year's Eve This Year Dänk 42Ø <dank@nugget.org> - 2017-01-02 07:08 +0000
      Re: 'Leap Second' to Be Added on New Year's Eve This Year Keith Thompson <kst-u@mib.org> - 2017-01-01 23:46 -0800
        Re: 'Leap Second' to Be Added on New Year's Eve This Year Dänk 42Ø <dank@nugget.org> - 2017-01-02 21:56 +0000
          Re: 'Leap Second' to Be Added on New Year's Eve This Year Keith Thompson <kst-u@mib.org> - 2017-01-02 15:38 -0800
      Re: 'Leap Second' to Be Added on New Year's Eve This Year "James R. Kuyper" <jameskuyper@verizon.net> - 2017-01-03 20:26 -0500

Page 1 of 5  [1] 2 3 4 5  Next page →

#100032 — 'Leap Second' to Be Added on New Year's Eve This Year

'Leap Second' to Be Added on New Year's Eve This Year

Full story: <http://www.space.com/33361-leap-second-2016-atomic-clocks.html>

  Revelers will get to celebrate New Year's Eve for a tiny bit longer 
than usual this year.

A "leap second" will be added to the world's official clocks on Dec. 31 
at 23 hours, 59 minutes and 59 seconds Coordinated Universal Time (UTC), 
which corresponds to 6:59:59 p.m. EST; the clocks will read 23:59:60 
before ticking over to midnight. The goal is to keep two different 
timescales in sync with each other.

The units of time had long been defined based on Earth's rotation 
relative to distant celestial bodies. But that changed with the 
invention of atomic clocks in the mid-20th century; scientists then 
decided to base the second on the natural vibrations of the cesium atom. 
[How to Build the Most Accurate Atomic Clocks (Video)]

These two timescales don't match up exactly, however. Measurements show 
that, because the moon's gravitational pull and other factors are 
gradually slowing Earth's spin, the rotation-based scale loses between 
1.5 and 2 milliseconds per day compared to atomic time — meaning the two 
diverge by a full second every 500 to 750 days.

Leap seconds are a way to make up for this difference. Since 1972, the 
International Earth Rotation and Reference Systems Service (IERS) — the 
organization that keeps track of time for the world — has added 26 leap 
seconds to atomic clocks, with the last such insertion coming on June 
30, 2015.

  The aim is to keep the two timescales within 0.9 seconds of each other.

"We can easily change the time of an atomic clock, but it is not 
possible to alter the Earth's rotational speed to match the atomic 
clocks," officials with the U.S. Naval Observatory (USNO), which 
maintains the Department of Defense's master clock, noted — wryly, it 
would seem — in a statement today (July 6).

While Earth's rotation rate is slowing, the effect is quite subtle.

"Confusion sometimes arises over the misconception that the occasional 
insertion of leap seconds every few years indicates that the Earth 
should stop rotating within a few millennia," USNO officials wrote. 
"This is because some [people] mistake leap seconds to be a measure of 
the rate at which the Earth is slowing. The 1-second increments are, 
however, indications of the accumulated difference in time between the 
two systems."

When leap seconds are added, they are always inserted on June 30 or Dec. 
31 of a particular year. In 1972, IERS officials called for a leap 
second to be inserted on both dates.

[toc] | [next] | [standalone]

#100033

In article <o3gl85$j26$1@dont-email.me>,
 "Mr. Man-wai Chang" <toylet.toylet@gmail.com> wrote:

> 'Leap Second' to Be Added on New Year's Eve This Year

NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!

2016 has lasted long enough! NOT ONE SECOND LONGER!

-- 
:-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted.
'I desire mercy, not sacrifice.'
Free the Amos Yee one.
Yeah, too bad about your so-called life. Ha-ha.

[toc] | [prev] | [next] | [standalone]

#100034

On 22/12/2016 9:48 PM, Siri Cruise wrote:
>> 'Leap Second' to Be Added on New Year's Eve This Year
>
> NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!
>
> 2016 has lasted long enough! NOT ONE SECOND LONGER!
>

Would this event hurt all installed Windows 10? :)

[toc] | [prev] | [next] | [standalone]

#100132

On 22 Dec 2016, Siri Cruise wrote
(in article<chine.bleu-C58C6A.05482722122016@news.eternal-september.org>):

> In article<o3gl85$j26$1@dont-email.me>,
> "Mr. Man-wai Chang" <toylet.toylet@gmail.com> wrote:
> 
> > 'Leap Second' to Be Added on New Year's Eve This Year
> 
> NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!
> 
> 2016 has lasted long enough! NOT ONE SECOND LONGER!

On the plus side, one second longer sleep/new year party.

-- 
Popularize the elitism!

[toc] | [prev] | [next] | [standalone]

#100138

In article <0001HW.1E0EA5EF0116D04B7000024503BF@nntp.idecnet.com>,
 Krzysztof Mitko <invalid@kmitko.at.list.dot.pl> wrote:

> On 22 Dec 2016, Siri Cruise wrote
> (in article<chine.bleu-C58C6A.05482722122016@news.eternal-september.org>):
> 
> > In article<o3gl85$j26$1@dont-email.me>,
> > "Mr. Man-wai Chang" <toylet.toylet@gmail.com> wrote:
> > 
> > > 'Leap Second' to Be Added on New Year's Eve This Year
> > 
> > NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!
> > 
> > 2016 has lasted long enough! NOT ONE SECOND LONGER!
> 
> On the plus side, one second longer sleep/new year party.

Isn't bad enough that US presidential election years are longer by one full day 
(29 Feb)? Not one more second!

-- 
:-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted.
'I desire mercy, not sacrifice.'
Free the Amos Yee one.
Yeah, too bad about your so-called life. Ha-ha.

[toc] | [prev] | [next] | [standalone]

#100051

On 12/22/2016 07:43 AM, Mr. Man-wai Chang wrote:
> 'Leap Second' to Be Added on New Year's Eve This Year
>
> Full story:
> <http://www.space.com/33361-leap-second-2016-atomic-clocks.html>
>
>  Revelers will get to celebrate New Year's Eve for a tiny bit longer
> than usual this year.
>
> A "leap second" will be added to the world's official clocks on Dec. 31
> at 23 hours, 59 minutes and 59 seconds Coordinated Universal Time (UTC),
> which corresponds to 6:59:59 p.m. EST; the clocks will read 23:59:60
> before ticking over to midnight. The goal is to keep two different
> timescales in sync with each other.

[snip]

It you're watching your computer's clock approaching UTC midnight, what 
should you expect to see? Would there be a 23:59:60, or would 23:59:59 
last for 2 seconds instead of one? I've heard its the latter, but am not 
sure.

BTW, I'm in central time, so global midnight is at 6PM.

-- 
3 days until the winter celebration (Sunday December 25, 2016 12:00:00
AM for 1 day).

Mark Lloyd
http://notstupid.us/

"To talk intelligibly about modern physics, we have to admit the
possibility of uncaused events." Taner Edis, Is Anybody Out There?

[toc] | [prev] | [next] | [standalone]

#100077

In article <zKW6A.231838$Uz2.141850@fx29.iad>,
 Mark Lloyd <not@mail.invalid> wrote:

> On 12/22/2016 07:43 AM, Mr. Man-wai Chang wrote:
> > 'Leap Second' to Be Added on New Year's Eve This Year
> >
> > Full story:
> > <http://www.space.com/33361-leap-second-2016-atomic-clocks.html>
> >
> >  Revelers will get to celebrate New Year's Eve for a tiny bit longer
> > than usual this year.
> >
> > A "leap second" will be added to the world's official clocks on Dec. 31
> > at 23 hours, 59 minutes and 59 seconds Coordinated Universal Time (UTC),
> > which corresponds to 6:59:59 p.m. EST; the clocks will read 23:59:60
> > before ticking over to midnight. The goal is to keep two different
> > timescales in sync with each other.
> 
> [snip]
> 
> It you're watching your computer's clock approaching UTC midnight, what 
> should you expect to see? Would there be a 23:59:60, or would 23:59:59 
> last for 2 seconds instead of one? I've heard its the latter, but am not 
> sure.
> 
> BTW, I'm in central time, so global midnight is at 6PM.

Your computers clock doesn't know anything about the leap second, so it 
will tick over at midnight New Years just as it does every other night. 
When it next connects to a time server it will simply update itself to 
the correct time as it always does. However, the official NIST clocks 
will, as I understand it, go to 23:59:60.

I guess if you live in the GMT time zone, you'll need to throw an extra 
'1' into the countdown before cheering and throwing streamers.

[toc] | [prev] | [next] | [standalone]

#100079

Le 23/12/2016 à 15:34, Mark Storkamp a écrit :
>  However, the official NIST clocks 
> will, as I understand it, go to 23:59:60.
Yes, and that's why Calendar had such a hard time dealing with leap
seconds without raising Constraint_Error...

-- 
J-P. Rosen
Adalog
2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX
Tel: +33 1 45 29 21 52, Fax: +33 1 45 29 25 00
http://www.adalog.fr

[toc] | [prev] | [next] | [standalone]

#100672

On 12/23/2016 9:34 AM, Mark Storkamp wrote:
[...]
> Your computers clock doesn't know anything about the leap second, so it
> will tick over at midnight New Years just as it does every other night.
> When it next connects to a time server it will simply update itself to
> the correct time as it always does. However, the official NIST clocks
> will, as I understand it, go to 23:59:60.
>
> I guess if you live in the GMT time zone, you'll need to throw an extra
> '1' into the countdown before cheering and throwing streamers.

Just "be a programmer" and count to zero rather than 1:

    10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, Happy New Year!

--
Kenneth Brody

[toc] | [prev] | [next] | [standalone]

#100686

On Fri, 30 Dec 2016 11:17:59 -0500, Ken Brody <kenbrody@spamcop.net>
wrote:

[snip]

>Just "be a programmer" and count to zero rather than 1:
>
>    10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, Happy New Year!

     With an attitude like that, you might miss a lot of appointments
(or parties).

Sincerely,

Gene Wirchenko

[toc] | [prev] | [next] | [standalone]

#100705

On 12/30/2016 11:38 AM, Gene Wirchenko wrote:
> On Fri, 30 Dec 2016 11:17:59 -0500, Ken Brody <kenbrody@spamcop.net>
> wrote:
>
> [snip]
>
>> Just "be a programmer" and count to zero rather than 1:
>>
>>    10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, Happy New Year!
>
>      With an attitude like that, you might miss a lot of appointments
> (or parties).

So you know of some New Year's parties that last for 1 second or less?

>
> Sincerely,
>
> Gene Wirchenko
>


-- 
If "he who lives by the sword shall die by the sword" holds true, then
jesus the carpenter met his end properly. After all, he was nailed to a
piece of wood, wasn't he?

[toc] | [prev] | [next] | [standalone]

#100701

On 12/30/2016 10:17 AM, Ken Brody wrote:

[snip]

> Just "be a programmer" and count to zero rather than 1:
>
>    10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, Happy New Year!
>

So "Happy New Year" comes AFTER 0 rather than AT 0.

> --
> Kenneth Brody
>


-- 
Mark Lloyd
http://notstupid.us/

Losing your faith is a lot like losing your virginity you don't realise
how irritating it was 'til it's gone.

[toc] | [prev] | [next] | [standalone]

#100708

On Fri, 30 Dec 2016 11:17:59 -0500, Ken Brody <kenbrody@spamcop.net>
wrote:

>On 12/23/2016 9:34 AM, Mark Storkamp wrote:
>[...]
>> Your computers clock doesn't know anything about the leap second, so it
>> will tick over at midnight New Years just as it does every other night.
>> When it next connects to a time server it will simply update itself to
>> the correct time as it always does. However, the official NIST clocks
>> will, as I understand it, go to 23:59:60.
>>
>> I guess if you live in the GMT time zone, you'll need to throw an extra
>> '1' into the countdown before cheering and throwing streamers.
>
>Just "be a programmer" and count to zero rather than 1:
>
>    10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, Happy New Year!


That should be 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, Happy New Year!

Or perhaps, 1001, 1000, 111, 110, 101, 100, 11, 10, 1, 0, Happy New
Year!

[toc] | [prev] | [next] | [standalone]

#100714

On 2016-12-30, Ken Blake <Ken@invalid.news.com> wrote:
> On Fri, 30 Dec 2016 11:17:59 -0500, Ken Brody <kenbrody@spamcop.net>
> wrote:
>
>>On 12/23/2016 9:34 AM, Mark Storkamp wrote:
>>[...]
>>> Your computers clock doesn't know anything about the leap second, so it
>>> will tick over at midnight New Years just as it does every other night.
>>> When it next connects to a time server it will simply update itself to
>>> the correct time as it always does. However, the official NIST clocks
>>> will, as I understand it, go to 23:59:60.
>>>
>>> I guess if you live in the GMT time zone, you'll need to throw an extra
>>> '1' into the countdown before cheering and throwing streamers.
>>
>>Just "be a programmer" and count to zero rather than 1:
>>
>>    10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, Happy New Year!
>
>
> That should be 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, Happy New Year!
>
> Or perhaps, 1001, 1000, 111, 110, 101, 100, 11, 10, 1, 0, Happy New
> Year!

Digital designer: 100, 101, 111, 110, 010, 011, 001, assert HNY.

[toc] | [prev] | [next] | [standalone]

#101072

On 12/22/2016 03:31 PM, Mark Lloyd wrote:
> On 12/22/2016 07:43 AM, Mr. Man-wai Chang wrote:
>> 'Leap Second' to Be Added on New Year's Eve This Year
>>
>> Full story:
>> <http://www.space.com/33361-leap-second-2016-atomic-clocks.html>
>>
>>  Revelers will get to celebrate New Year's Eve for a tiny bit longer
>> than usual this year.
>>
>> A "leap second" will be added to the world's official clocks on Dec. 31
>> at 23 hours, 59 minutes and 59 seconds Coordinated Universal Time (UTC),
>> which corresponds to 6:59:59 p.m. EST; the clocks will read 23:59:60
>> before ticking over to midnight. The goal is to keep two different
>> timescales in sync with each other.
>
> [snip]
>
> It you're watching your computer's clock approaching UTC midnight, what
> should you expect to see? Would there be a 23:59:60, or would 23:59:59
> last for 2 seconds instead of one? I've heard its the latter, but am not
> sure.
>
> BTW, I'm in central time, so global midnight is at 6PM.

Few clocks are designed to display leap seconds. They are of negligible 
importance for most ordinary timekeeping purposes. If you were looking 
at a clock showing central time (zone -6) with leap seconds, then you 
should have seen 17:59:59 followed by 17:59:60 followed by 18:00:00.

For the kinds of programming I do, leap seconds are significant. We're 
required to calculate the ground position of every pixel in the 
satellite images we process with an accuracy of +/- 50m, and handling 
leap seconds incorrectly would cause an error of about 7500m, because 
that's how far the satellites move in one second, so we were very 
careful to write our code to handle leap seconds correctly.

Unfortunately, the relevant hardware clock doesn't implement leap 
seconds correctly, which rendered all of our careful coding irrelevant. 
Instead of going 23:59:59, 23:59:60, 00:00:00, it went 23:59:59, 
00:00:00, 00:00:01. The last erroneous time stamp was 00:00:03.252105Z. 
Some time after that the clock jumped backwards by exactly one second, 
putting it back in sync with UTC. The first timestamp received after the 
reset was 00:00:03.223224Z. I cannot narrow down the reset time more 
precisely than that - but I know from experience with previous leap 
seconds that the reset probably did NOT occur precisely at 00:00:03 UTC. 
The clock was deliberately designed to do this, because (for reasons 
that have not yet been explained to me) it wasn't feasible to make it 
implement leap seconds correctly.

[toc] | [prev] | [next] | [standalone]

#100052

In article <o3gl85$j26$1@dont-email.me>, toylet.toylet@gmail.com says...
> A "leap second" will be added to the world's official clocks on Dec. 31 
> at 23 hours, 59 minutes and 59 seconds Coordinated Universal Time (UTC), 
> 

Google has an interesting approach to this to make sure that the 1-
second adjustment doesn't cause problems. They "smear" the change over a 
longer period of time: 

https://googleblog.blogspot.com/2011/09/time-technology-and-leaping-
seconds.html

[toc] | [prev] | [next] | [standalone]

#100053

On Thursday, December 22, 2016 at 5:14:15 PM UTC-5, Jason wrote:
> In article <o3gl85$j26$1@dont-email.me>, toylet.toylet@gmail.com says...
> > A "leap second" will be added to the world's official clocks on Dec. 31 
> > at 23 hours, 59 minutes and 59 seconds Coordinated Universal Time (UTC), 
> > 
> 
> Google has an interesting approach to this to make sure that the 1-
> second adjustment doesn't cause problems. They "smear" the change over a 
> longer period of time: 
> 
> https://googleblog.blogspot.com/2011/09/time-technology-and-leaping-
> seconds.html

With all of the digital technology we have these days, and with people
relying on their computers and phones for the time, why can't our society
smear the daylight savings hour over a long period of time so our days
are just constantly reflecting accurately our target daylight portion?

Best regards,
Rick C. Hodgin

[toc] | [prev] | [next] | [standalone]

#100054

Jason wrote:
> In article <o3gl85$j26$1@dont-email.me>, toylet.toylet@gmail.com says...
>> A "leap second" will be added to the world's official clocks on Dec. 31 
>> at 23 hours, 59 minutes and 59 seconds Coordinated Universal Time (UTC), 
>>
> 
> Google has an interesting approach to this to make sure that the 1-
> second adjustment doesn't cause problems. They "smear" the change over a 
> longer period of time: 
> 
> https://googleblog.blogspot.com/2011/09/time-technology-and-leaping-
> seconds.html
> 

Neat idea. Although most services can handle a 1-second blip. One
sensitive service is mail servers. Old dovecot v1.x did not handle
discrepancies well, but only when time "goes backwards" and for more and
one second. Took several second offset and the server would crash and
need to restart the service.

-- 
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[toc] | [prev] | [next] | [standalone]

#100103

On Thu, 22 Dec 2016 17:40:35 -0500 "Jonathan N. Little" 
<lws4art@gmail.com> wrote in article <o3hkmg$e6m$1@dont-email.me>
> Neat idea. Although most services can handle a 1-second blip.
> 

Google reported that there is some kind of lock required with multiple 
servers that can't handle the sudden 1-second change. That's what 
motivated them to adopt the smearing scheme.

[toc] | [prev] | [next] | [standalone]

#100105

On Fri, 23 Dec 2016 19:57:25 -0500, Jason <jason_warren@ieee.org> wrote:

>On Thu, 22 Dec 2016 17:40:35 -0500 "Jonathan N. Little" 
><lws4art@gmail.com> wrote in article <o3hkmg$e6m$1@dont-email.me>
>> Neat idea. Although most services can handle a 1-second blip.
>> 
>
>Google reported that there is some kind of lock required with multiple 
>servers that can't handle the sudden 1-second change. That's what 
>motivated them to adopt the smearing scheme.

For the networking gear that has an issue dealing with leap seconds,
it's not the leap second itself that causes problems. It's the *notice*
that a leap second is coming. Certain NTP clients totally choke when
they get that flag. It doesn't seem like it would be a big deal, but
it's a big deal, indeed. That's why leap smearing avoids the problem.
With smearing, there's no flag.

[toc] | [prev] | [next] | [standalone]

Page 1 of 5  [1] 2 3 4 5  Next page →

Back to top | Article view | comp.lang.c

csiph-web