Hi,
In OSuse 11.4 this file had 50GB size in my comptuer.>:) I have installed 12.1 and I see It’s a 34MB size and It seems It’s growing, my question is: Is it a normal behavior?
Last time I did the following:
rm .xsession_errors
touch .xsession_errors
chattr -i .xsession_errors
Is it a good practice?
Is there another way to avoid these sizes??
Cheers!.
The file should be
“.xsession-errors” and not
“.xsession_errors”.
That might have just been a posting typo by you. But check.
My “.xsession-errors” is currently 40345 bytes long.
The file is supposed to be recreated as a new empty file for every login.
I hope you are are using a unix file system, not NTFS, for home directories.
I would not remove and recreate that file during a GUI session. You could try
cp /dev/null .xsession-errors
That truncates the file back to size zero, but in some circumstance that doesn’t work the way you would expect, so try it and monitor the file for a while afterwards.
Either you have a broken application that is creates far too many errors, or you never logout from your x-session, or something is broken.
On 11/21/2011 12:46 PM, Bezoutsidentity wrote:
> In OSuse 11.4 this file had 50GB size in my comptuer.>:)
i’m using openSUSE 11.4 (is that what you mean when you type OSuse
11.4?) and i don’t even have an .xsession_errors file, and neither do i
have an
xsession_errors
…xsession_errors
…Xsession_errors
…Xsession_error
…xsession_error
so, tell me where yours is located and i’ll look again…
also, please tell us the desktop environment you are using…and, did
you ever do an ‘upgrade’ laying openSUSE over any pre-existing linux
distribution (i’m trying to understand how you have one and i don’t!)
or maybe your machine is on a network with non-Linux boxes…
confused!!
On 11/21/2011 02:16 PM, nrickert wrote:
> I hope you are are using a unix file system, not NTFS, for home
> directories.
@Bezoutsidentity, please show us the terminal input/output from
df -h
cat /etc/fstab
copy/paste the in/output back to this thread using the instructions
here: http://goo.gl/i3wnr
–
DD http://tinyurl.com/DD-Caveat
dump Flash: http://www.bbc.co.uk/news/technology-15797399
Hi,
I’m sorry. Yes, it was a typo, the file name is .xsession-errors and yes Osuse is opensuse.
I had gnome in Opensuse 11.4 now I have KDE in 12.1.
My computer doesn’t usually turn off, that’s the problem.
My fstab is this:
/dev/disk/by-id/ata-SAMSUNG_SP2504C_S09QJ1ML600354-part3 swap swap defaults 0 0
/dev/disk/by-id/ata-SAMSUNG_SP2504C_S09QJ1ML600354-part1 / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-SAMSUNG_SP2504C_S09QJ1ML600354-part2 /home ext4 defaults 1 2
/dev/md0 /mnt/raid512 ext4 defaults 1 2
/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246J90Z188159-part1 /mnt/sd1024 ext4 defaults 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
Cheers!
> My computer doesn’t usually turn off, that’s the problem.
ok! you know the problem…so, you should know the solution too…right?
this is not rocket science (once you know the problem!)…
just log out of the session, and then log back in (no need to boot, or
shutdown–just log out and in) and a new xsession-errors will be created…
–
DD
Hi,
Wouldn’t there be a way to limit the size of .xsession-errors?
I wouldn’t like to log out any time It starts to grow.
Anyway, In KDE it doesn’t seem to grow as much as in gnome.
Am 22.11.2011 18:56, schrieb Bezoutsidentity:
>
> Hi,
>
> Wouldn’t there be a way to limit the size of .xsession-errors?
>
> I wouldn’t like to log out any time It starts to grow.
>
> Anyway, In KDE it doesn’t seem to grow as much as in gnome.
>
>
I would report it as a bug. Now you may ask why:
When reading your thread I first thought “OK if it grows so much some
application (or more applications) is running wild and spams the log,
the user should fix that”
But thinking a second time about it brings me to the point that NO
application whatsoever and as crappy as it may be should be able to fill
up your disk space until the user hits the quota or if there is no quota
until your account has 0 bytes left available.
This is a security risk.
–
PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.7.3 |
nVidia ION | 3GB Ram
But who’s in charge of this(.xsession-errors file)?
This file is part of X11, isn’t it?
Am 23.11.2011 12:26, schrieb Bezoutsidentity:
>
> But who’s in charge of this(.xsession-errors file)? This file is part
> of X11, isn’t it?
>
This is a bit difficult for me since I am not a real expert. What I
remember is that it really depends on the desktop environment (or more
precise the login manager) who is in charge of that file.
All in all it is of course more or less X11 itself.
–
PC: oS 11.4 (dual boot 12.1) 64 bit | Intel Core i7-2600@3.40GHz | KDE
4.6.0 | GeForce GT 420 | 16GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.7.3 |
nVidia ION | 3GB Ram
I’m pretty sure that stderr is redirected to this file at the start of your session. The effect is that errors from most GUI windows automatically go here. Nobody is in charge. It’s just gathering the stderr stuff that is produced by normal programs when they report an error.
It is basically a crude way of dealing with software error message that you normally don’t want to see but that could occasionally be useful for debugging.
I never stay logged in for more than around 4 days, so this does not cause a problem for me (because the file is truncated at login).
If you make “.xsession-errors” a symlink to “/dev/null” then that might work to just toss all of the error messages. But you would need to logout then login again for that change to be effective.
Then, we have to check it out regularly It doesn’t grow too many.
Thanks for your help.