operating time

    The systemd journal includes OS information and /storage/.kodi/temp/kodi.log contains activities by Kodi. Activities with the application are not necessariily representative of activities of a user though, so you have to interpret the logs.

    Thank you for your reply "chewitt".

    Indeed, the activity log is not representative of the activity because there are few dates that are recorded.

    Is there another possibility to know the raspberry turned on and when it turned off.

    Otherwise I saw in libreelec that it displays the activity time over 6 days. there is no possibility to see the details of these 6 days?

    In LE11 (nightly) images (and maybe LE10 .. I can't guarantee though) allow you to configure persistent journal logs. It's intended for debugging but in your case will simply increase the time range there is data for. You will be able to see boot and can see login/logout activities in the journal, but another issue to contend with on RPi is the lack of RTC which means the clock on boot starts from glibc release date not actual time; until the network is up an ntp corrects. You can solve that by adding an RTC chip.

    Another approach would be to configure Syslog export of data and track activity in a logger/SIEM tool. You will still need a solution for RTC issues, but when you see gaps in telemetry the Pi was off, and when it's on you get data.

    That was my idea yesterday too, but no, uptime displays the last time you booted the box (only the current season) and nothing from the past.

    with continuous logging switched on:

    journalctl --list-boots

    might do

    Edited once, last by GDPR-7 (January 26, 2022 at 1:26 PM).