New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log files should be moved out of /run/user/<UID>/xpra #3725
Comments
Sure, but I'm not going to work on this - feel free to submit a PR.
OK, but not cleaned up automatically.
That's only for root. |
Your reasoning indeed has some practical and historical justification. The issue is that Xorg.log grows pretty fast. This is an issue with long running user sessions. It would likely not affect me personally (I have 64 GB of RAM =] ) but conceptually present design can be improved.
Someone's decision to keep
What about having an option to specify log file location via arguments/config file? The only reason I wrote this enhancement proposal was because I didn't find this configuration option available. BTW, I truly appreciate your work!!!!! |
The one we use for xpra should not.
You can already move the Xorg log file using a config file, in my
Tweak |
Is your feature request related to a problem? Please describe.
Log files (
Xorg.log
,server.log
) need to be moved from/run/user/<UID>/
/XDG_RUNTIME_DIR
directories. Suitable locations could user based directories (e.g.XDG_DATA_HOME
) or standard/var/log
directories.The filesystem under
/run/user/
istmpfs
. It is situated in RAM. Use recommendations for that directory include temporary storage of PIDs, sockets, etc, session information, configuration files - all with consideration to be small.LOG
files belong on the opposite side of the size spectrum. Occasionally they tend to grow fast and for that reason often are placed on separate partitions altogether.Describe the solution you'd like
Possible suitable LOG location candidates
XDG_DATA_HOME
XDG_CACHE_HOME
/var/log
directoriesAlternatively LOG file location could be configurable via cmd arguments or configuration file(s).
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: