Over 300 free and legal portable apps, up-to-date, & new apps weekly (Jun 14, 2013: Opera Mail). Please contribute today!.
PortableApps.com Carbide: Military-grade hardware-encryption, water/shock/dust/tamper-resistant, 5 years antivirus+warranty!
It's safest, most secure USB flash drive on Earth. And it comes with PortableApps.com and your name on it. Starting at $94.95!

1234567890 seconds since Unix epoch

Bahamut's picture
Bahamut - February 5, 2009 - 3:23am

It will have been 1234567890 seconds since the Unix epoch in just over a week.
$ date -d '1970-01-01 UTC 1234567890 seconds' to get the time for your time zone (for GNU/Linux).


( categories: )

0447:54 on 13 Feb. '09?

It was at 0447:54 or did I calculate wrong? Here's my proof. Just used the basic Windows calculator so it didn't save all the calculations or let me copy/paste and no way am I doing all that again, but here's how I ran the numbers...

1234567890 seconds
/60 to see what that is in minutes
/60 to see what that is in hours
/24 to see what that is in days
/365.25 to see what that is in years, accounting for leap years (39 and change)
-39 because we've got the year, 2009, leaves us with 44 and change
-31 for January, leaves us with 13 and change
-13 because we've got the exact date, leaves us with a long decimal number
*24 to see what hour it is, we get 4 and change
-4 since we now know the hour
*60 to see what the minute is, we get 47 and change
-47 since we know the minutes
*60 to see the seconds...
...but that leaves me with 54... and change. It should even out to an integer. So I messed up somewhere or Windows rounded it off somewhere.

/365.25 to see what that is

/365.25 to see what that is in years

There's your problem. There's actually less than that in a year.

Vintage!