Willy Tarreau wrote:
quoted text
>> The per-user system would also be nice for servers, provided there are
>> CPU/disc IO/swapper/... quotas or priorities at least.
>>     
>
> This is too hard to adjust. Imagine what would happen to your hundreds of
> apache processes when the "backup" user will start the rsync or tar+gzip,
> or when user "root" will start rotating and compressing the logs. Being
> able to group processes may be useful on servers, but it should be enabled
> on purpose by the admin.
>   

Sure, if implemented, it should default to the old behavior to avoid 
surprises.  Maintenance jobs may have to be niced to avoid getting too 
much cpu.  But it should also make hosting different applications on the 
the server much more predictable and easier (think of your hundreds of 
apache processes swamping an unrelated load when slashdotted).

-- 
error compiling committee.c: too many arguments to function

-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/