]] Lars Wirzenius | On su, 2010-08-15 at 14:19 +0200, Tollef Fog Heen wrote: | > I would guess they still fill up the .xsession-errors file, though? At | > least for me, that file is mostly useless due to: | > | > « ...Too much output, ignoring rest... » | > | > as the last line. | | It's pretty clear to me that both .xsession-errors and the stderr of GUI | apps are lousy ways of logging debugging messages. Something similar to | syslog for a per-user/per-session would be a very useful thing to have, | in my opinion.
FWIW, systemd (which can work both as an init replacement as well as a session manager) handles this by forwarding those to syslog (by default), which at least partially works around the problem of disks filling up. Priority is then set by the same convention as printk, that is, you do <4> Foo to log «Foo» at log level 4, aka warning. It'd be neat to have a way to post-mortem get at the logged output of an application and have that appear if you submit a bug report or similar. (Think bug-buddy in gnome or apport in Ubuntu.) -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/877hjqalv6....@qurzaw.linpro.no
