![]() xsession-errors >$(mktemp -tmpdir=.xsession-errors.backup/XXXXXX) xsession-errors in case, for some reason, truncate replaces the file without actually truncating the underlying file (this way you won't lose access to the file if it becomes unlinked without being deleted/truncated). Optional: Use a hard-link to create a second filename for. For diagnostic purposes, it might be worthwhile to tail the file before truncating. If you want to limit the space used for logging, you could do this in a loop or cron. I was able to recover the disk space using truncate. If after a reboot I check the /home/mkey/.xsession-errors file properties I will see that it now points to right where I want it /media/mkey/tmp/.xsession-errors and that it's being written to. The OS would already start writing to the /home location, so any redirects at that point were in vain. I found that I needed to run the script as a service as running it during startup would be too late. Finally, to install and run the service I used the followingĬp mkey_rvice /etc/systemd/system/mkey_rviceĬhmod 644 /etc/systemd/system/mkey_rvice.I have created a mkey_rvice fileĮxecStart=/bin/bash /home/mkey/mkey_custom.sh.Ln -sf /media/mkey/tmp/.xsession-errors.old /home/mkey/.xsession-errors.old Ln -sf /media/mkey/tmp/.xsession-errors /home/mkey/.xsession-errors Touch /media/mkey/tmp/.xsession-errors.old I have created a mkey_custom.sh script in my home directory.Tmpfs /media/mkey/tmp tmpfs size=10000000 0 0 I have put this in my /etc/fstab to create a 10MB RAM drive.After some days it's going to boost into overdrive and waste my writes. My primary concern here is that the log file is wasting my SSD writes since I like to keep up with long up-times and the issue exacerbates over time. This issue follows me around on Arch KDE, Neon KDE and now MX KDE. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |