Results 1 to 5 of 5

Thread: Huge errorlog?

  1. #1

    Exclamation Huge errorlog?

    Today I discovered a HUGE file in my home-folder, it was called ".xsession-error" and was a .txt file of 35,5GB!

    What could this be?

  2. #2
    Join Date
    Oct 2008
    Location
    Birmingham. AL
    Posts
    858

    Default Re: Huge errorlog?

    If you do a Web search on this, you'll see that it's a common complaint. (My own .xsession-error file is over 200KB, just for the record.) Do a "tail .xsession-error" and see if it isn't mostly "GTK" complaints. I'll bet it is.

    From that same Web search, you'll see that there are any number of causes, but the most common seem to be mixing GTK (Gnome) with KDE stuff. Firefox is known to do it depending on the theme chosen. The problem is that so many apps want to report *everything* to that file for debugging. Very useful in some cases, but in others, it does just create a mondo-monster-huge-O file that's really not that useful.

    Unless you're actually having problems, you can just delete it.

  3. #3
    ab@novell.com NNTP User

    Default Re: Huge errorlog?

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Considering the information from smpoole7 you MAY want to change it into a
    symlink pointing to something like /tmp/.yourUserName-xsession-error and
    hopefully everything that writes to it will just send data to /tmp. You
    MAY then want to set /tmp to be cleared on a reboot, which I do not
    believe is the default for SUSE but you can change it easily enough:

    http://forums.opensuse.org/archives/...mp-folder.html

    Anyway I am not sure of all the ramifications of this but unless you've
    been running for a LONG time you may have an application needlessly
    spilling its guts (almost literally) to that file. If nothing else create
    a cron job for yourself to delete it every week or so.

    Note that the first solution above only works if you reboot regularly,
    which isn't exactly the status quo in Linux unless you have a weird need
    to (battery dying on a laptop for example).

    Good luck.





    smpoole7 wrote:
    > If you do a Web search on this, you'll see that it's a common complaint.
    > (My own .xsession-error file is over 200KB, just for the record.) Do a
    > "tail .xsession-error" and see if it isn't mostly "GTK" complaints. I'll
    > bet it is.
    >
    > From that same Web search, you'll see that there are any number of
    > causes, but the most common seem to be mixing GTK (Gnome) with KDE
    > stuff. Firefox is known to do it depending on the theme chosen. The
    > problem is that so many apps want to report *everything* to that file
    > for debugging. Very useful in some cases, but in others, it does just
    > create a mondo-monster-huge-O file that's really not that useful.
    >
    > Unless you're actually having problems, you can just delete it.
    >
    >

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v2.0.9 (GNU/Linux)
    Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

    iQIcBAEBAgAGBQJJ0YCEAAoJEF+XTK08PnB5kjEP/jxmyVumEzzCsaBOl+cSkALP
    Gyudu5fFrUdoIjEoC1YF7kXUOmjKZhLJYAAnciyo+DE2+np8azE+mFImJGXm9PU3
    W3+dnH5TamiFP+uhl/s4JR4hxao9aLP1SIWJ3SZO4p9Rm3Km8tZAkVME8X6A4o8z
    Xc78i6fBaABlO/yXnmn73uQbm04vgeicTmoYN1DBWyshKRJcQC77Q5iEhVyP6s49
    nNT1i5xw4yLrlY3EEF0dtWBlaIA+zvcpFo5GoqD4c7L906TO031d5jCw0RgQUpQ5
    C+Wo97CLptMRtzIDlzrN0OXVKssRpDJ/pYp8Pr0IWa8Mg6rbsAfSwIixLAG8q47x
    OF7JX8je9umiIUicP2xLXkzsvN1nX1zwrT6RXFlf1/Iszz4iLAKyaGoXnd/FXEl9
    FLzgJEFqOzYRRpBqddq+YvxbP5h0GiiqRvF6MrAg1/P4xm5U/tKvdCrafT8/e8yV
    YLQorlWc8q0KP51usvEt/1BLHat+u3agdTvDOmWPnGzdrJQrpSt7ctAFqfoBEqn2
    HAvBDFb2Lspavj4ngpMR3CaimeZ/C40MCtsBiwvqy/MqOPYvmpTh6oS4TL/Ra2G1
    TlaaK64zq3GJURQJjosd7dmZ83KFXA3TwAoV10v66Go33TSHoqSFMY7hwgj6Ogdp
    H/nIGh1zEEBvxz1qqCT9
    =HPNl
    -----END PGP SIGNATURE-----

  4. #4
    Join Date
    Jun 2008
    Location
    /dev/belgium
    Posts
    1,946

    Default Re: Huge errorlog?

    Quote Originally Posted by ab@novell.com View Post
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Considering the information from smpoole7 you MAY want to change it into a
    symlink pointing to something like /tmp/.yourUserName-xsession-error and
    hopefully everything that writes to it will just send data to /tmp. You
    MAY then want to set /tmp to be cleared on a reboot, which I do not
    believe is the default for SUSE but you can change it easily enough:

    the /tmp folder - openSUSE Forums

    Anyway I am not sure of all the ramifications of this but unless you've
    been running for a LONG time you may have an application needlessly
    spilling its guts (almost literally) to that file. If nothing else create
    a cron job for yourself to delete it every week or so.

    Note that the first solution above only works if you reboot regularly,
    which isn't exactly the status quo in Linux unless you have a weird need
    to (battery dying on a laptop for example).
    or just make a symlink to /dev/null like I did
    Let the black hole swallow it all

  5. #5
    Join Date
    Oct 2008
    Location
    Birmingham. AL
    Posts
    858

    Default Re: Huge errorlog?

    I guess someone could make the argument that it's useful in the event that you do have a problem. Maybe another idea would be to put in a Cron job that deletes it daily.

    Swerdna has a how-to on Cron that will help, if the OP isn't familiar with it.

    Cron Tables (Crontab) in Suse / openSUSE [Event Scheduler for 10.x, 11.x]

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •