Idea: Automatically save one set of logs in a Samba share

I was thinking about the troubleshooting process, and I was reading some of the threads where @gouchi helps new users gain SSH access in order to generate logs. It seems that if users didn’t have to learn SSH and how to restart RetroArch in verbose mode, that would streamline troubleshooting quite a bit.

Therefore would it make sense for Lakka to save one complete set of logs somewhere that is accessible over Samba? I don’t suggest an archive of logs that builds up over time, just logs from the current session, or perhaps the current session and the previous session.

What do folks think?

2 Likes

I wish we generated a log file by default. The new Windows installer package includes shortcuts to launch RA with --log-file log.txt added to the launch line.

But yeah, I think having it generate a log.txt file somewhere that’s easily accessible via SMB (edit: not SSH, durr) would be good/useful.

I told @Kivutar that we should try to do a script like alsa-info.sh which will still required to login with ssh.

Your idea is interesting generate by default a log accessible by sftp/smb +1

You can mount directories through a system.d service: http://wiki.openelec.tv/index.php?title=Mounting_network_shares

1 Like

@markwkidd please open an issue so that we don’t forget about this feature request :wink:

Thank you.

For Lakka you can simply log to /var/log then you will get the log together with everything else through the “Logfile” SMB share which automatically creates tarballs from /var/log.

1 Like

Thanks for the feedback everyone!

@gouchi I have created an Issue on github as you suggested: https://github.com/libretro/Lakka-LibreELEC/issues/189

1 Like