Török Edwin <edwin+ml-cerowrt@etorok.net> writes:

> I haven't upgraded to -12 yet (still on -9), but logread doesn't seem
> to get its time updated: Sat Jan 17 03:41:38 1970 authpriv.notice
> dropbear[3747]: Pubkey auth succeeded for 'root' with key md5
> 2a:6d:49:b6:74:91:9c:34:f8:7a:2e:40:65:b2:e9:e9 from
> 172.30.42.12:52391
>
> Although the date is right:
> # date
> Mon Mar 24 22:05:20 GMT 2014
>
> I tried running sysfixtime manually, or just run the 'date -s
> <unix-timestamp>' manually, with no luck. Any idea how to get logread
> (or well the daemon/kernel) to update its timestamps?

Sysfixtime only touches the system clock. Just checked on my box, and I
have the same issue with the logs. The system log is managed by ubusd
these days, but neither kicking that or the log daemon itself seems to
get the timings right on a 'logread'.

Interestingly, running logread -f outputs the incoming events with the
right timestamps; so I guess it's a bug somewhere that fails to get the
offset for old events or something...

Found this in the openwrt HEAD git log:

commit 345c4805ee324b4a34bd60c8f5762f0b6dd27497
Author: blogic <blogic@3c298f89-4303-0410-b956-a3cf2f4a3e73>
Date:   Tue Mar 18 19:22:38 2014 +0000

    ubox: update to latest git head
    
    logread now shows the right time.
    
    Signed-off-by: John Crispin <blogic@openwrt.org>
    
    git-svn-id: svn://svn.openwrt.org/openwrt/trunk@39951 3c298f89-4303-0410-b956-a3cf2f4a3e73

Which is newer than -9 but older (I think; the tag is missing from
github) than -12. So an upgrade should probably fix it :)

*off to upgrade my own install*

-Toke