On Fri, 28 Oct 2011, "Peter Ross" <Peter.Ross@bogen.in-berlin.de> wrote:
Maybe it would be good to have something like plymouth take over the .xsession-errors. Send that data to a pipe which is read by a program that displays the last few megs of data instead of all of it.
Good old syslog maybe? "Message repeated x times" is already built-in.
That doesn't work for the situation where you have a set of three or more messages repeated or for the situation where you have 1000 variants of the same message (EG the same message repeated for each file in a directory or each memory address of an object that wasn't liked). On Fri, 28 Oct 2011, "Peter Ross" <Peter.Ross@bogen.in-berlin.de> wrote:
I just wanted to start working - and deleted it. It did not happen since.
That's a bad idea. When an open file is deleted there is no way (*) to reclaim the disk space except killing every process that has a handle for it - which means logging out at a minimum. "echo -n > file" is the correct thing to do in such situations. (*) Well you could attach a debugger to a process which has an open file handle and make it call ftruncate(2). But for a typical user that's impossible. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/