How would I re-direct the out of this to /dev/null or have it not record at all?

Would a softlink work? I can't do a hardlink since they are on different partitions.

Well, I fixed the root problem (it was a kde 4 issue) but am still interested if anyone has an answer.

(That file would grow about 20 gig an hour.)

I was once annoyed by xsession flood, I changed this line (In /etc/X11/Xsession)


# attempt to create an error file; abort if we cannot
if (umask 077 && touch "$ERRFILE") 2> /dev/null && [ -w "$ERRFILE" ] &&
[ ! -L "$ERRFILE" ]; then
chmod 600 "$ERRFILE"
elif ERRFILE=$(tempfile 2> /dev/null); then
if ! ln -sf "$ERRFILE" "${TMPDIR:=/tmp}/xsession-$USER"; then
message "warning: unable to symlink \"$TMPDIR/xsession-$USER\" to" \
"\"$ERRFILE\"; look for session log/errors in" \
"\"$TMPDIR/xsession-$USER\"."
fi
else
errormsg "unable to create X session log/error file; aborting."
fi

#remove xsession-errors
#exec >>"$ERRFILE" 2>&1
exec &> /dev/null

There are maybe cleaner ways of doing it but didn't find really.

Weeks later, I had problems with an X client and without this log, you can't really see anything, so I reverted my modification.

I don't think you can create softlinks or anything, if you look at the previous lines. It will abort if it cannot create $HOME/.xsession-errors or create a tmpfile in TMPDIR.

Do you mean the .Xsession or the .xsession-errors file grows? Why would the non-error one grow at all?

The values of those files are defined in /etc/X11/Xsession, so theoretically, you could redirect output to /dev/null from there. Anyhow, it's this section in /etc/X11/Xsession that you would want to muck with (maybe):Never mind: I see that nx5000 has a fuller explanation of what I was (half-)thinking of.