Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #228253 > unrolled thread

The .xsession-errors problem

Back to article view | Back to linux.debian.user

Contents

  The .xsession-errors problem Teemu Likonen <tlikonen@iki.fi> - 2020-10-26 17:50 +0100
    Re: The .xsession-errors problem Reco <recoverym4n@enotuniq.net> - 2020-10-26 18:10 +0100
      Re: The .xsession-errors problem Teemu Likonen <tlikonen@iki.fi> - 2020-10-27 16:10 +0100
        Re: The .xsession-errors problem rhkramer@gmail.com - 2020-10-27 20:20 +0100
    Re: The .xsession-errors problem Sven Joachim <svenjoac@gmx.de> - 2020-10-26 18:20 +0100
      Re: The .xsession-errors problem Teemu Likonen <tlikonen@iki.fi> - 2020-10-26 19:10 +0100
    Re: The .xsession-errors problem Linux-Fan <Ma_Sys.ma@web.de> - 2020-10-26 19:30 +0100
    Re: The .xsession-errors problem Tixy <tixy@yxit.co.uk> - 2020-10-27 00:10 +0100
      Re: The .xsession-errors problem John Hasler <jhasler@newsguy.com> - 2020-10-27 00:30 +0100
      Re: The .xsession-errors problem Greg Wooledge <wooledg@eeg.ccf.org> - 2020-10-27 13:00 +0100
        Re: The .xsession-errors problem Andrei POPESCU <andreimpopescu@gmail.com> - 2020-10-27 14:50 +0100
          Re: The .xsession-errors problem David <bouncingcats@gmail.com> - 2020-10-28 05:30 +0100
            Re: The .xsession-errors problem Andrei POPESCU <andreimpopescu@gmail.com> - 2020-10-28 12:50 +0100
            Re: The .xsession-errors problem Celejar <celejar@gmail.com> - 2020-10-28 19:40 +0100
              Re: The .xsession-errors problem David <bouncingcats@gmail.com> - 2020-10-29 00:10 +0100
                Re: The .xsession-errors problem Curt <curty@free.fr> - 2020-10-29 19:30 +0100
                  Re: The .xsession-errors problem David <bouncingcats@gmail.com> - 2020-10-30 01:00 +0100
    Re: The .xsession-errors problem David Wright <deblis@lionunicorn.co.uk> - 2020-10-27 01:00 +0100
      Re: The .xsession-errors problem David <bouncingcats@gmail.com> - 2020-10-27 01:30 +0100
        Re: The .xsession-errors problem Greg Wooledge <wooledg@eeg.ccf.org> - 2020-10-27 13:00 +0100
          Re: The .xsession-errors problem David Wright <deblis@lionunicorn.co.uk> - 2020-10-29 18:40 +0100
    Re: The .xsession-errors problem Anders Andersson <pipatron@gmail.com> - 2020-11-01 11:20 +0100
      Re: The .xsession-errors problem Teemu Likonen <tlikonen@iki.fi> - 2020-11-01 17:50 +0100
        Re: The .xsession-errors problem Kenneth Parker <sea7kenp@gmail.com> - 2020-11-01 18:40 +0100

Page 2 of 2 — ← Prev page 1 [2]

#228384

On Tue 27 Oct 2020 at 07:53:01 (-0400), Greg Wooledge wrote:
> On Tue, Oct 27, 2020 at 11:28:12AM +1100, David wrote:
> > On Tue, 27 Oct 2020 at 10:56, David Wright <deblis@lionunicorn.co.uk> wrote:
> > >       fuser -v "$j"
> > >       [ $? -ne 0 ] && gzip "$j" && mv -i "$j.gz" "$HOME/.monitors/xsession/"
> > 
> > > (Script improvements always appreciated.)
> 
> > https://www.shellcheck.net says:
> > """
> > Line 2:
> > [ $? -ne 0 ] && echo hi
> >   ^-- SC2181: Check exit code directly with e.g. 'if mycmd;', not
> > indirectly with $?.
> > """
> 
> In other words, instead of writing:
> 
> fuser -v thing
> [ $? != 0 ] && other thing && third thing
> 
> You can write it this way:
> 
> if ! fuser -v thing; then
>   other thing &&
>   third thing
> fi
> 
> The $? form isn't technically *wrong*, but it's awkward, and doesn't
> let you have an "else" action.

Thanks to you both for reminding me of shellcheck. I think I've got a
few of these to correct in .bashrc too. Running shellcheck on .bashrc
is always a horror show.

Ironically, though, there is one slight advantage to the explicit test
of $? in my .xsession (because it's run with   set -x   in force):
the result of the test is reflected in the log. With the improved
construction, the result has to be deduced by checking which subsequent
commands run (or which branch is taken when there's an else clause).

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#228406

On Mon, Oct 26, 2020 at 5:43 PM Teemu Likonen <tlikonen@iki.fi> wrote:
>
> It seems that ~/.xsession-errors file can still grow to infinity in
> size. Sometimes it grows really fast. This is nothing new: we have all
> seen it and talked about it. What do you do to maintain this file?
>
>   - Do you just delete it when you happen to notice it's too big?
>
>   - Do you configure some rotating system, perhaps with logrotate(8)?
>     (Why doesn't Debian have this automatically?)
>
>   - Do you add it to your backup system's ignore list so that a
>     potentially big file doesn't fill your backups?
>
>   - What do Debian documentation and faq lists teach about maintaining
>     this potentially huge file?
>
>   - Why is it normal that in Debian (and GNU/Linux) you need to manually
>     delete a hidden file to keep it from filling your hard disks?
>
> Note that I'm not necessarily looking for help but different views are
> welcome. I'm mostly interested in the phenomenon that there still is
> this well-known indefinitely growing file and seemingly no automatic
> rotation.
>
> From my backups I found an ~/.xsession-errors file of size 111
> megabytes. Probably I deleted the file at that point and it started grow
> again.

Amateur. I found a 24 GB .xsession-errors once, on a 30 GB filesystem.
423 million lines. Most of them the same:

(indicator-weather:2201): LIBDBUSMENU-GLIB-CRITICAL **:
dbusmenu_menuitem_build_variant: assertion `DBUSMENU_IS_MENUITEM(mi)'
failed

Buggy crap can fill it up pretty fast.

[toc] | [prev] | [next] | [standalone]

#228413

[Multipart message — attachments visible in raw view] — view raw

* 2020-11-01 11:09:50+01, Anders Andersson wrote:

> On Mon, Oct 26, 2020 at 5:43 PM Teemu Likonen <tlikonen@iki.fi> wrote:
>> From my backups I found an ~/.xsession-errors file of size 111
>> megabytes. Probably I deleted the file at that point and it started
>> grow again.
>
> Amateur. I found a 24 GB .xsession-errors once, on a 30 GB filesystem.
> 423 million lines.

That is some log file. One would probably want to introduce it to the
nice /dev/null device:

    ln -sf /dev/null ~/.xsession-errors

Graphical programs are sometimes really noisy when started from command
line. And there are various output lines related to dbus, kdeinit5 and
other fancy desktop stuff which nobody understands anymore.

-- 
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 4E1055DC84E9DFF613D78557719D69D324539450

[toc] | [prev] | [next] | [standalone]

#228414

[Multipart message — attachments visible in raw view] — view raw

On Sun, Nov 1, 2020, 11:48 AM Teemu Likonen <tlikonen@iki.fi> wrote:

> * 2020-11-01 11:09:50+01, Anders Andersson wrote:
>
> > On Mon, Oct 26, 2020 at 5:43 PM Teemu Likonen <tlikonen@iki.fi> wrote:
> >> From my backups I found an ~/.xsession-errors file of size 111
> >> megabytes. Probably I deleted the file at that point and it started
> >> grow again.
> >
> > Amateur. I found a 24 GB .xsession-errors once, on a 30 GB filesystem.
> > 423 million lines.
>
> That is some log file. One would probably want to introduce it to the
> nice /dev/null device:
>
>     ln -sf /dev/null ~/.xsession-errors
>
> Graphical programs are sometimes really noisy when started from command
> line. And there are various output lines related to dbus, kdeinit5 and
> other fancy desktop stuff which nobody understands anymore.
>

Also, verify that Debug Mode is not set.  (I once did that with the Linux
Kernel, years ago, and it filled up the Partition!)

Kenneth Parker

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web