The worst thing that could happen ist that they move processes arround all the time, but that should not cause much trouble except more load.
He should connect to all of them. I'm currently rewriting this module for better connection and lesser crude code ;-)
1. A program is only 'bad' when resources run into limitation. Currently only a memory protector exists and if he detects memory pressure, the largest programs are put into memory limitations.
I documented the default scheduler. As you can see, it does not say: this process is bad, but tries to find groups that belong together and gives each group an amount of cpu shares. As opposed the normal: each process gets the same amount of cpu share.
The rules in rules/media.lua schould set a flag on your mp3 program, so it gets more cpu share because it fits the requirements of the media group.
I'm running it all the time, but i will not suggest running it on a server currently. But for a desktop box it's fine.
Sure. If you run ulatencyd you can run tests/memleak for example without your box crashing. Or try something creazy like compiling the linux kernel with make -j 40 ;-)
I personally find by desktop much more smoother when it's running.
Added it to the wiki, thanks.
I just want to thank you for your answers, I'm satisfied with them... thanks