Errors logged to /tmp/runcommand.log ...OK ... WHERE?
-
Soooo how do you check the "errors logged to /tmp/runcommand.log" ?
Apologies for the very n00bish question but it seems I am the only person who did not burst forth from the womb with this knowledge... and after several hours of exhaustive search it does not seem to be documented anywhere.
-Is there a full path name I'm missing?
-Does the splashscreen forget a game-name wildcard? (i.e. Errors logged to /snes/wizardofoz/tmp/runcommand.log)
-Does temp folder and possibly the text file need established by the user prior to any actual log writing by EmulationStation?Thank you ahead of time.
-
@PullingMyHair that is the full path. to access it, you need to look into SFTP or command line access. try https://github.com/RetroPie/RetroPie-Setup/wiki/Transferring-Roms#sftp-needs-an-active-internet-connection
-
I would have suggested to “wait for a soul with a red crystal on Deborah Cliff”, but I didn't want to get punched.
-
I just want to add that there are a lot of error situations that actually do not result in anything being written to that particular log file.
I think it just pertains to any error that occurs during the runcommand script. Errors after that (occuring in RetroArch for instance) will not be included there. -
@Zigurana said in Errors logged to /tmp/runcommand.log ...OK ... WHERE?:
I just want to add that there are a lot of error situations that actually do not result in anything being written to that particular log file.
I think it just pertains to any error that occurs during the runcommand script. Errors after that (occuring in RetroArch for instance) will not be included there.sure they will :) errors handled by libretro cores are dumped to the console, which the log retains.
-
@dankcushions well, that's good to know. I better check the permissions then, because i have never spotted anything in the logfile.
-
I noticed today after updating Retropie that the runcommand box now says it logs to "/dev/shm/runcommand.log"
Any idea what that is all about? Can I just edit the /opt/retropie/supplementary/runcommand.sh and change it to /tmp/runcommand.cfg ?
-
What's the problem with the new location ? I moved the log to ram - one less thing to write to the sdcard (plus performance if say there is a log of debug output).
-
@BuZz No problem whatsoever, I just didn't understand it. I've done some quick research and now I understand the reasons for moving the log file to that location.
Makes perfect sense to me now that I understand it (ie: I'm new to Linux).
Thank you.
-
@brenthunter2005 TBH it won't make much difference probably, and we still unpack zips to the sdcard (That requires more thought to move, as some archives would be a bit large to unpack in memory - at least on some RPI models). I might add a configuration option for that though.
I might consider a config to shift system logs into ram also.
-
I also spent some time yesterday searching for the runcommand.log file looking for some advancemame loading issues.
please whenever possible update the documentation so to let clear that it can be in /tmp/ or also in /dev/shm.https://github.com/retropie/retropie-setup/wiki/runcommand
Thanks
-
@rulmismo It was moved to /dev/shm quite a long time ago - when launching it states where the log is btw.
The wiki is user editable btw. feel free to update if you think this is needed.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.