[prev] [thread] [next] [lurker] [Date index for 2006/07/04]
I have a suspended valgrind process and a running make process, and nothing to do. So I decide to run tuxracer to enjoy the performance hiccups (so what if I have 2 CPUs for the 2 running processes? it still hangs for a while once in 10 seconds), and maybe to hit a couple of trees with Tux's head (it's usually him doing it to me, so excuse my cruelty). Linux reads my mind and logs me out. Out of memory, no doubt. Why not kill the process instead of the user? Is "security" the lame excuse this time - prevention of denial of service attacks? It's *my* desktop machine, damn it, it has no other users! Of course I lost the history of the 10 shells I was running, and was left with a completely useless one from hell knows when. Saving the history of several shells under files named just like the "session name" is apparently a notoriously hard problem - after all, 20 years are not enough to solve it.There's stuff above here
Generated at 09:01 on 07 Jul 2006 by mariachi 0.52