Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by acqq on Tuesday May 13, 2014 @02:39AM
(#7736785)
Did anybody notice Sun, 09 Sep 2001 01:46:40 GMT, when it was 10000....? And why looking at decimal values, anybody calculated when we have some nice binary timestamps?
[ Parent
| on HN ]
Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by cperciva on Tuesday May 13, 2014 @02:59AM
(#7736826)
The FreeBSD Project actually had a gigasecond bug -- the cvsup protocol (used for CVS tree replication and checkouts) transmitted time as an ASCII seconds-since-epoch value, and when September 2001 arrived, the changed string length caused a protocol sanity check to fail.
Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by alephnil on Tuesday May 13, 2014 @04:04AM
(#7736996)
Yes. In java at the time if you wrote a number with 9 or less digits, it would always be considered to be an int. If the number was above 1 billion (10 digits), you had to end it with an L (1000000000L), probably since it possibly could overflow an int.
We had a trial version of our software that would expire after 30 days. To make that we had a script that inserted the expiry date into the source and recompiled every night. Around 30 days before it passed 1 billion the compiler started to give an error, and the script crashed.
(It may actually have been 12->13 digits, since java use milliseconds since the epoch, but I'm not so sure this many years later)
Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by dribnet on Tuesday May 13, 2014 @04:26AM
(#7737059)
Yes, this was on the radar then as Y2k was still fresh in everyone's memory.
[1] "S1B coming" http://tech.slashdot.org/story/01/04/17/1915221/the-quickly-...
[2] "Any Billennium Bugs?" http://tech.slashdot.org/story/01/09/10/0353238/billenniums-...
Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by mrrazz on Tuesday May 13, 2014 @03:32AM
(#7736913)
Yes, I remember it fondly, celebrating the 'billennium' on IRC:
Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by thret on Tuesday May 13, 2014 @03:57AM
(#7736978)
Thanks for posting this.
Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by slyall on Tuesday May 13, 2014 @03:33AM
(#7736915)
Openldap got hit by the billennium bug. I remember because we told our Noc to keep an eye open (Sunday afternoon where we were) and we started getting alerts that all LDAP replication was broken.
http://www.openldap.org/lists/openldap-bugs/200109/msg00052....
Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by eCa on Tuesday May 13, 2014 @04:24AM
(#7737050)
Yes.. I ran a small service started in 2000 that saved epoch times in a varchar column. Sorting on time turned funky for a short while.
Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by settrans on Tuesday May 13, 2014 @02:50AM
(#7736806)
Or perhaps Fri, 13 Jul 2012 11:01:20 GMT, unix time 0x50000000? Developers using MongoDB at the time were likely to notice.
Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by stingraycharles on Tuesday May 13, 2014 @03:16AM
(#7736868)
Could you elaborate? I couldn't find anything about that timestamp in relation to MongoDB.
Re:Today at 16:53:20 GMT, it'll be 1400000000 in Unix time.
by petercooper on Tuesday May 13, 2014 @04:29AM
(#7737064)
BSON object IDs contain a 4 byte timestamp so perhaps it'd be directly visible on those.