Strange future file stamps

[MymsMan]

It appears that during initialization the humax screws up its time zone settings and instead of creating file time stamps with GMT or BST time actually creates files with GMT+2 - double summer time but later corrects to using BST.

Note the files that have future time stamps.
I booted the the system at 11:30 BST / 10:30 GMT

Humax /mnt/hd2/mod/flexview/webif/plugin/flexview # date
Sat Apr 16 12:25:34 BST 2016
Humax /mnt/hd2/mod/flexview/webif/plugin/flexview # ls /tmp --time-style=full-iso -t
total 185
-rw-------  1 root root     0 2016-04-16 12:30:52.000000000 +0100 .rractive
-rw-r--r--  1 root root     0 2016-04-16 12:30:49.000000000 +0100 .humaxtv.running
-rw-------  1 root root     1 2016-04-16 12:30:49.000000000 +0100 .lbr
-rw-r--r--  1 root root   548 2016-04-16 12:30:49.000000000 +0100 rsvsync.log
-rw-r--r--  1 root root  2779 2016-04-16 12:30:49.000000000 +0100 xinit.log
-rw-------  1 root root     3 2016-04-16 12:30:48.000000000 +0100 .tz
drwxrwxrwt  2 root root   940 2016-04-16 12:25:32.000000000 +0100 .
-rw-rw-rw-  1 root root     0 2016-04-16 12:25:14.000000000 +0100 .webiflock_flatview
-rw-rw-rw-  1 root root     0 2016-04-16 12:25:01.000000000 +0100 .webiflock_webif_auto
...
-rw-r--r--  1 root root  0 2016-04-16 11:31:11.000000000 +0100 webif-error.log
-rw-r--r--  1 root root  49 2016-04-16 11:31:11.000000000 +0100 webif.log
-rw-r--r--  1 root root  38 2016-04-16 11:31:08.000000000 +0100 hosts
-rw-r--r--  1 root root  0 2016-04-16 11:31:08.000000000 +0100 if-up
drwxr-xr-x 18 root root  183 2015-03-04 23:22:00.000000000 +0000 ..
-rw-r--r--  1 root root  4 2000-01-01 00:00:05.000000000 +0000 dnsmasq.pid
-rw-r--r--  1 root root  6 2000-01-01 00:00:05.000000000 +0000 ifstate
-rw-r--r--  1 root root  13 2000-01-01 00:00:04.000000000 +0000 banner.log
-rw-r--r--  1 root root  0 2000-01-01 00:00:04.000000000 +0000 utmp

Shortly after this the system hung and booting from cold I didn't get the time stamps in the future

-rw-r--r--  1 root root    49 2016-04-16 13:17:21.000000000 +0100 webif.log
-rw-r--r--  1 root root    38 2016-04-16 13:17:18.000000000 +0100 hosts
-rw-r--r--  1 root root     0 2016-04-16 13:17:18.000000000 +0100 if-up
drwxr-xr-x 18 root root   183 2015-03-04 23:22:00.000000000 +0000 ..
-rw-------  1 root root     0 2000-01-01 00:00:08.000000000 +0000 .rractive
-rw-r--r--  1 root root     0 2000-01-01 00:00:06.000000000 +0000 .humaxtv.running
-rw-------  1 root root     1 2000-01-01 00:00:05.000000000 +0000 .lbr
-rw-r--r--  1 root root     4 2000-01-01 00:00:05.000000000 +0000 dnsmasq.pid
-rw-r--r--  1 root root     6 2000-01-01 00:00:05.000000000 +0000 ifstate
-rw-r--r--  1 root root   428 2000-01-01 00:00:05.000000000 +0000 rsvsync.log
-rw-r--r--  1 root root  2784 2000-01-01 00:00:05.000000000 +0000 xinit.log
-rw-r--r--  1 root root    13 2000-01-01 00:00:04.000000000 +0000 banner.log
-rw-r--r--  1 root root     0 2000-01-01 00:00:04.000000000 +0000 utmp

The reason I am looking closely at these time stamps is chaseget uses the is-up time stamp to determine whether to put the system into standy and last night a recording ended at 01:40 but at 01:50 the standby check found the if-up time stamp to be 01:45 and so didn't put the system into standby as expected.

16/04/2016 01:40:25 DA(11655)- done...processed /media/My Video/Rude Tube_ Clan Anarchy_20160416_0043.ts in 3238.736s 00:53:59 - 4 ad breaks detected
...
16/04/2016 01:50:02 - CG(16497)- Last boot time 01:45:06
16/04/2016 01:50:02 - CG(16497)- Boot time 01:45:06 > Awakened time 00:48:40 - quit

This is the first time I have found the is-up file mtime to be anything other than the last boot time; what could have changed it?

 

[MymsMan]

I am now switching to use uptime to calculate the system boot time rather than using file time stamps

set lastboot $([clock seconds] - round([system uptime]))