<SiFuh>
remiliascarlet: Well, it is half full if you are filling it and half empty if you emptying. And if you don't know then it is automatically half full because it started its existence empty.
farkuhar has joined #opencrux
<farkuhar>
Never mind filling up a glass, it's more interesting to watch a 180GB /home partition being filled by ~/.xsession-errors when you leave a browser opened on a website that triggers incessant warnings about seccomp violations.
<farkuhar>
Maybe the ulimit command would have prevented the runaway growth of ~/.xsession-errors. In the meantime, redirecting the browser's stdout and stderr to /dev/null is an easy fix, although it could be regarded as akin to "using a sledgehammer to kill an ant".
<farkuhar>
On the other hand, I can't remember the last time I learned anything useful from the browser's stdout or stderr, so maybe redirecting them to /dev/null won't ever be an issue.
<farkuhar>
SiFuh: Yes, that snippet is the same as what gets shipped with xorg-xinit in CRUX. So you can force the use of /tmp rather than /home, simply by making ~/.xsession-errors read-only.
<SiFuh>
farkuhar: I had xsession-errors in an mfs file system.
<SiFuh>
Memory File System. So virtual memory
<farkuhar>
But I don't consider it much of an improvement to fill up /tmp or virtual memory with 180GB of browser warnings. I'd much rather cut it off at the root, and redirect all the browser output to /dev/null.
<SiFuh>
farkuhar: Could always do logrotation. Can't remeber how to do it in Linux
<farkuhar>
I'm trying to recall which website I left opened for so long yesterday, that triggered all those warnings about seccomp violations. Probably Bing maps or something interactive like that.
<SiFuh>
In OpenBSD it is done crontab and uses newsyslog and there is a config file for it under /etc/
SiFuh has quit [Remote host closed the connection]