Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming > #7236
| Subject | Re: 'Leap Second' to Be Added on New Year's Eve This Year |
|---|---|
| Newsgroups | alt.comp.hardware.pc-homebuilt, comp.lang.c, comp.lang.ada, comp.programming, alt.os.linux.ubuntu |
| References | <o3gl85$j26$1@dont-email.me> <GoGdnf_on-zkYfTFnZ2dnUU7-X3NnZ2d@earthlink.com> <lnpok5x5tz.fsf@kst-u.example.com> |
| From | Dänk 42Ø <dank@nugget.org> |
| Organization | THC |
| Date | 2017-01-02 21:56 +0000 |
| Message-ID | <zNudnUt2Lts1UffFnZ2dnUU7-WHNnZ2d@earthlink.com> (permalink) |
Cross-posted to 5 groups.
On 01/02/2017 07:46 AM, Keith Thompson wrote: > Dänk 42Ø <dank@nugget.org> writes: > [...] >> My question is how this will affect computer programs that convert Unix >> Julian time (which keeps time in seconds since 00:00:00 UTC 01 Jan >> 1970). > > That's just Unix time; it's not "Julian". > >> For example, I have various Perl modules that convert Unix time to >> readable timestamps. If my module doesn't include for the leap second, >> will my timestamps be one second off? I assume they'll update the >> myriad of programming language modules, but how long will this take? >> For now, I'll assume the current Perl module has been updated. > > Typically Unix systems ignore leap seconds. For example, on my system's > timestamp as I write this is 1483342650, though allowing for the 37 > intervening leap seconds, 1970-01-01 00:00:00 UTC was actually > 1483342687 seconds ago. The slightly incorrect representation of old > date isn't much of a problem in practice. > > The system clock was probably adjusted gradually during the period > before and after the leap second. But since computers store files with Unix time strings, how is is that a recently saved file shows the correct current time and is not 37 seconds off? Obviously, the software is accounting for those leap seconds? Or maybe you're referring to the SYSTEM time, which is adjusted, but makes dating really old files difficult since I don't what system they came from or whether they adjusted for leap seconds. A very trivial matter, especially with old files, but a very important one today, where files are timestamped down to the milli- second. >> (BTW, I was watching the Berlin clock on timeanddate.com, and their >> clock went from 23:59:59 to 00:00:00 -- there was no "23:59:60"). > > time.gov showed 23:59:60. Shoulda gone there. I was especially interested in Berlin's New Year, as I was following the German news to see whether a terrorist attack occurred at that moment.
Back to comp.programming | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
'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 "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 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 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 Gene Wirchenko <genew@telus.net> - 2017-01-05 09:20 -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 10:26 -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 raltbos@xs4all.nl (Richard Bos) - 2017-01-09 17:12 +0000
Re: 'Leap Second' to Be Added on New Year's Eve This Year Har-dee-har-har <YouMustBeKidding@This.Com> - 2017-01-09 09:53 -0800
Re: 'Leap Second' to Be Added on New Year's Eve This Year "J-P. Rosen" <rosen@adalog.fr> - 2017-01-10 07:20 +0100
Re: 'Leap Second' to Be Added on New Year's Eve This Year "James Wilkinson Sword" <imvalid@somewear.com> - 2017-01-12 23:17 +0000
Re: 'Leap Second' to Be Added on New Year's Eve This Year Tim <timothybil@yahoo.com> - 2017-01-13 00:51 -0600
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
csiph-web