[Dave] > [quoted lines by Lars Bjørndal on 2016/04/29 at 16:34 +0200] > > >After more digging, I find that the problem occures on a Raspberry pi > >only, and not on a pc that I tried. Restarting BRLTTY from the rpi > >doesn't make any difference. > > Did you start it directly from a logged in command line, or did you start it > with a service manager like systemd? I'm wondering what time it shows if > started directly from a command line.
Oh, I see. I did `systemctl restart brltty'. When starting BRLTTY directly, it shows the correct time. So this was solved by using timedatectl to set correct time zone. > >> Do the timestamps in a brltty debug log match those on the status display? > >> In > >> other words, do they have the same error? > > > >No. > > To confirm: Are you saying that the very same brltty is showing different > times > in its log file (the one created by the -L option) than it is on the status > display? When using the -L swithc, the time is the same. So again, problem solved. Thank you. Lars _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
