Bash convert epoch to date, showing wrong time

Question

How come date is converting to wrong time?

result=$(ls /path/to/file/File.*) #/path/to/file/File.1361234760790 currentIndexTime=${result##*.} echo "$currentIndexTime" #1361234760790 date -d@"$currentIndexTime" #Tue 24 Oct 45105 10:53:10 PM GMT

Roughly 43164 + 1970 ~= 45105 (43135.8 + 1970 to be more accurate) so the date is right — perreal
– perreal, Commented May 1, 2013 at 2:09
using epochconverter.com, i get GMT: Tue, 19 Feb 2013 00:46:00 GMT which is desired result — bobbyrne01
– bobbyrne01, Commented May 1, 2013 at 2:21

andrewdotn · Accepted Answer · 2013-05-01 02:17:05Z

139

This particular timestamp is in milliseconds since the epoch, not the standard seconds since the epoch. Divide by 1000:

$ date -d @1361234760.790 Mon Feb 18 17:46:00 MST 2013

answered May 1, 2013 at 2:17

andrewdotn

35.3k10 gold badges110 silver badges134 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Laeeq Over a year ago

Yes, its due to timestamp in milliseconds. I have also checked here epochconvert.com and get correct result Tuesday, 19 February 2013, 12:46:00 AM GMT

Marcus · Accepted Answer · 2019-03-20 22:05:14Z

For Mac OS X, it's date -r <timestamp_in_seconds_with_no_fractions>

$ date -r 1553024528 Tue Mar 19 12:42:08 PDT 2019

or

$ date -r `expr 1553024527882 / 1000` Tue Mar 19 12:42:07 PDT 2019

or

$ date -r $((1553024527882/1000)) Tue Mar 19 12:42:07 PDT 2019

armatita · Accepted Answer · 2016-06-01 17:10:09Z

You can use bash arithmetic expansion to perform the division:

date -d @$((value/1000))

Note that "value" is a bash variable with the $ being optional; i.e., $value or value can be used.

Collectives™ on Stack Overflow

Bash convert epoch to date, showing wrong time

3 Answers 3

1 Comment

Comments

Comments

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

Comments

Comments

Related