Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Countdown to timestamp 1,500M

timestamp.online

Post reply on HN
Print view View original

21–30 of 62 posts

Re: Countdown to timestamp 1,500M

#22

Post by evv »

amptorn wrote: post #17
nitramm wrote: post #4

But be aware with your celebration. It can be slightly off due to leap seconds. https://unix.stackexchange.com/questions/327361/openbsd-6-0-...

A leap second coming between now and Unix time 1500000000 would certainly be unexpected. I doubt any software in the world is ready for that.

Really, your organization isn't prepared to handle an emergency leap second? Tsk, tsk.. /s

Re: Countdown to timestamp 1,500M

#23

Post by loader »

netcraft wrote: post #5

some info to save someone else from having to look it up 1 400 000 000 was 5/13/2014, 11:53:20 AM 1 600 000 000 will be 9/13/2020, 7:26:40 AM 1 000 000 000 was 9/8/2001, 8:46:40 PM 2 000 000 000 will be 5/17/2033, 10:33:20 PM 2^32-1 (4 294 967 295) will be 2/7/2106, 12:28:15 AM 100 million seconds is a little over 3 years 1 billion seconds is almost 32 years.

Also 2038-01-19 https://en.wikipedia.org/wiki/Year_2038_problem

Re: Countdown to timestamp 1,500M

#25

Post by twic »

netcraft wrote: post #5

some info to save someone else from having to look it up 1 400 000 000 was 5/13/2014, 11:53:20 AM 1 600 000 000 will be 9/13/2020, 7:26:40 AM 1 000 000 000 was 9/8/2001, 8:46:40 PM 2 000 000 000 will be 5/17/2033, 10:33:20 PM 2^32-1 (4 294 967 295) will be 2/7/2106, 12:28:15 AM 100 million seconds is a little over 3 years 1 billion seconds is almost 32 years.

You have skipped over one interesting date between 2e9 and 2^32-1 - 2038-01-19T03:14:07:

https://en.wikipedia.org/wiki/Year_2038_problem

Although perhaps you have assumed that everyone already knows it!

Re: Countdown to timestamp 1,500M

#26

Post by schoen »

sbierwagen wrote: post #13
denysonique wrote: post #10

Earlier quoted context omitted.

On UNIX likes systems*. Pro-tip: `watch -n 1 date +%s` will give you a live view of the timestamp

If you have an X server installed, you can also get a windowed unix time clock: xclock -utime -update 1

I tried this and noticed that you forgot -digital, which is apparently necessarily for -utime to have any effect.

Re: Countdown to timestamp 1,500M

#27

Post by bluesmoon »

netcraft wrote: post #5

some info to save someone else from having to look it up 1 400 000 000 was 5/13/2014, 11:53:20 AM 1 600 000 000 will be 9/13/2020, 7:26:40 AM 1 000 000 000 was 9/8/2001, 8:46:40 PM 2 000 000 000 will be 5/17/2033, 10:33:20 PM 2^32-1 (4 294 967 295) will be 2/7/2106, 12:28:15 AM 100 million seconds is a little over 3 years 1 billion seconds is almost 32 years.

timestamp is stored as a signed value since it can also go backwards from the epoch, so you need 2^31-1

Re: Countdown to timestamp 1,500M

#29

Post by sector777 »

netcraft wrote: post #5

some info to save someone else from having to look it up 1 400 000 000 was 5/13/2014, 11:53:20 AM 1 600 000 000 will be 9/13/2020, 7:26:40 AM 1 000 000 000 was 9/8/2001, 8:46:40 PM 2 000 000 000 will be 5/17/2033, 10:33:20 PM 2^32-1 (4 294 967 295) will be 2/7/2106, 12:28:15 AM 100 million seconds is a little over 3 years 1 billion seconds is almost 32 years.

I remember 1e+9 because it shifted a log file over by 1 character. And less than a week later I was out of a job (travel industry).
Post reply on HN