Hi.
I've been using peruser module for a couple of months, and have noticed some
unpleasant details.
First of all, there's a problem with file descriptor openning when more than
1024. I have coped with it doing so - "put in apachectl ulimit -n 10000 and
raising FD_SETSIZE in /usr/include/linux/posix_types.h"
The second problem is such - when working without restarting daemon Apache
for some time, its restart (apachectl -k restart) takes about 10 mins and is
followed with a high load of the server ~ LA 1500 ( i didn't notice such
problems with other versions of Apache prefork or worker).
The third problem I faced is such: when reaching the limit of 96 processes
by one of the users, LA also jumps and new processes for other users are
created in a slower way and these processes are characterised of high CPU
capacity.
My peruser config:
<IfModule peruser.c>
PidFile /var/run/apache.pid
LockFile /var/run/accept.lock
ServerLimit 1024
MaxClients 1024
MinSpareProcessors 16
MaxProcessors 96
MaxRequestsPerChild 1000
# kill idle processors after this many seconds (0 to disable)
IdleTimeout 60
# kill hung processes after this many seconds (0 to disable)
ExpireTimeout 300
Multiplexer www daemon
# chroot dir is optional:
# Processor user group
</IfModule>
And the last problem: deals with limitation of CPU time for user's process.
I tried to launch Apache с ulimit -t 20 - and it worked. I requested
script, that makes high loading on CPU after that user process is killed,
but instead of it appears a new one and works 20с. And can happen up to 5
times. What is the reason of it?
System: Linux 2.6.20 x86-64, Apache 2.2.3
--
BRGDS. Alexey Vlasov.
_______________________________________________
Peruser mailing list
[email protected]
http://www.telana.com/mailman/listinfo/peruser
