On Mon, May 30, 2011 at 4:40 AM, steven <[email protected]> wrote: > > On Mon, 2011-05-30 at 17:59 +0800, Pei Lin wrote: > > 2011/5/30 steven <[email protected]>: > > > > > > On Mon, 2011-05-30 at 10:15 +0200, Andre Klapper wrote: > > >> On Mon, 2011-05-30 at 16:05 +0800, steven wrote: > > >> > currently when uxlauncher start a new user session, it will redirect > > >> > stderr/stdout to file xsession-errors, and all x client will write > their > > >> > log messages to this file, and this file will get too big in one > > >> > power-up cycle > > >> > > >> Please define "too big" by providing numbers, and why you think it is > > >> actually too big... > > >> > > > > > > 400M > > > > I think first should check where and why so huge errors coming from > > and not only redirect errors to /dev/null. > > Finding the reason is more important that workaround something. > > One trick method can be as that "ln -s /dev/null ~/.xsession-errors" > this looks nice, but I think it's very convenient for the user to log > messages to file or not. so does anyone want to give a comment on > whether to add the feature to uxlaunch or not? >
I will not merge such a change. Any program written to log 400MB of output to stdout/stderr is obviously written to do this on purpose, and throwing the output away would not help in any way at all. To be honest, the ~/.xsession-errors file should (in a production level installation) be mostly empty. But if it does fill up, as QA often finds, it's the only indicator that something really went wrong. Removing that indicator would not help anyone at all, and just makes bugs harder to detect. Auke
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
