Originally Posted by
ameerat42
Only other thing that falls into the head is that Linux is displaying them unexpectedly.
Can you (somehow) check how it is doing that? Can you set it to display as GMT in the
settings somewhere?
\\Well, you can stat the files. Here I have 2 files, one, IMG_0036.CR2, is straight from the camera. IMG_0035.CR2 has been 'touch"ed in linux to correct the time.
Code:
stat * File: IMG_0035.CR2
Size: 31302264 Blocks: 61184 IO Block: 32768 regular file
Device: b309h/45833d Inode: 486 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/ myuser) Gid: ( 1000/ myuser)
Access: 2018-07-01 10:00:00.000000000 +1000
Modify: 2018-07-01 13:06:52.000000000 +1000
Change: 2018-07-01 13:06:52.000000000 +1000
Birth: -
File: IMG_0036.CR2
Size: 30177451 Blocks: 58944 IO Block: 32768 regular file
Device: b309h/45833d Inode: 487 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/ myuser) Gid: ( 1000/ myuser)
Access: 2018-07-01 10:00:00.000000000 +1000
Modify: 2018-07-01 23:09:04.000000000 +1000
Change: 2018-07-01 23:09:02.000000000 +1000
The camera is definitely doing something odd. Just look at the output of ls -al. The file from the camera only has a date listed, and no associated time. I think it does this with a file that has a future time however.
Code:
$ ls -altotal 60128
drwxr-xr-x 2 myuser myuser 32768 Jul 1 13:10 .
drwxr-xr-x 4 myuser myuser 32768 Jul 1 2018 ..
-rw-r--r-- 1 myuser myuser 31302264 Jul 1 13:06 IMG_0035.CR2
-rw-r--r-- 1 myuser myuser 30177451 Jul 1 2018 IMG_0036.CR2