Hello.
If it already happened that you ran out of disk space and using the du
-k /home | sort -n | tail -5 command you were able to determine that
the .xsession-errors file is the one that takes up more space, the
first step to fix the problem is to empty it completely:
$ >~/.xsession-errors
Once the space is freed, you will want this situation not to be
repeated again in the future. To achieve this it is best to try to
find the origin of the problem, ie, to know which process is writing
uncontrolled to the error log and why.
If you want to forget about this log because in normal operation you
are not interested in its debugging information, you can redirect to
/dev/null everything that is written to it and thus always keep a size
of 0 bytes. For this you can delete the .xsession-errors file and
create a symbolic link to /dev/null instead in order to get the same
result:
$ rm .xsession-errors
$ ln -s /dev/null .xsession-errors
The problem is that when you restart the session the symbolic link
will be replaced back by a regular file and will start to grow again.
To avoid this you must add the following lines to the .bashrc in your
home directory:
# If the .xsession-errors file is not a symbolic link, delete it and
create it as such
if [ ! -h $HOME/.xsession-errors ]; then
/bin/rm $HOME/.xsession-errors
ln -s /dev/null $HOME/.xsession-errors
fi
2023-11-10, pn, 19:53 Thierry de Coulon via tde-users
<users(a)trinitydesktop.org> rašė:
On Friday 10 November 2023 16.14:16 phiebie--- via tde-users wrote:
The file is called .xsession-errors (mind the .
at the beginning).
Yep, that's it. But *any* file that is created in home and fills the space
would have the same result (for example some stuck copy routine or (I got
that too) a video capture software that (as most do) uses ~ as temp
directory.
That's why I avoid the one-partition-for-everything solution. It's easy to
link other partitions to home directories.
This monster indeed grows and grows and I have
not yet found the
culprit.
Solution: a cronjob daily just before I shutdown the system with [rm -f
.....] and the spook is gone.
Well, mine is only a few KB (today) and seems to be recreated at boot. I did
not do anything. I don't think this is a TDE stuff, so maybe it depends on
the distribution settings (MX-Linux here).
Thierry
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…