David Grossberg, one could extrapolate your position to every application that logs information. This viewpoint is unfortunately a cart before the horse. For example, why as a software maintainer (which viewed by all maintainers of every application, driver, etc. that this is an application issue, i.e. the log is filling up because either the sheer volume of the information, and/or the applicability of the log messages to maintaining the application) even worry about too verbose logging? Or logging things that are most important when reviewing the applicable log? Why don't all package developers have every possible thing spew out into any log they can, generating hundreds of GB/s, grinding your OS to a crawl, and giving an overwhelming amount of irrelevant information (low signal to noise ratio)? But don't worry about it, the operating system will take care of that, and people should just get used to manually intervening in log capture modifications of every possible application they have installed (~2566 installed on my instance so that's a lot of work!), but fast enough before the logging kicks in and stops their efforts due to the OS spending all its resources on just handling logs...
Long story short, file a report against the offending application and the bug in it will get addressed. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870138 Title: .xsession-errors fills hard drive until system crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/870138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
