Hello
Directive NiceLevel is not in list of directives, look:
*Module Name:* peruser.c <http://www.starhost.cz/server-info?peruser.c>
*Content handlers:* /none/
*Configuration Phase Participation:* Create Server Config
*Request Phase Participation:* Process Connection, Post-Read Request
*Module Directives:*
User - /Effective user id for this server/
Group - /Effective group id for this server/
ChrootDir - /The directory to chroot(2) into/
ListenBacklog - /Maximum length of the queue of pending connections,
as used by listen(2)/
Listen - /A port number or a numeric IP address and a port number,
and an optional protocol/
SendBufferSize - /Send buffer size in bytes/
ReceiveBufferSize - /Receive buffer size in bytes/
MinSpareProcessors - /Minimum number of idle children, to handle
request spikes/
MinSpareServers - /Minimum number of idle children, to handle
request spikes/
MaxSpareProcessors - /Maximum number of idle children, 0 to disable/
MaxClients - /Maximum number of children alive at the same time/
StartProcessors - /Number of child processors per vhost at startup/
MinProcessors - /Minimum number of processors per vhost/
MaxProcessors - /Maximum number of processors per vhost/
MaxCPUUsage - /Maximum CPU usage per active processor/
MinMultiplexers - /Minimum number of multiplexers the server can have/
MaxMultiplexers - /Maximum number of multiplexers the server can have/
ServerLimit - /Maximum value of MaxClients for this run of Apache/
ExpireTimeout - /Maximum time a child can live, 0 to disable/
IdleTimeout - /Maximum time before a child is killed after being
idle,0 to disable/
MultiplexerIdleTimeout - /Maximum time before a multiplexer is
killed after being idle, 0 to disable/
ProcessorWaitTimeout - /Maximum time a multiplexer waits for the
processor if it is busy/
Multiplexer - /Specify an Multiplexer Child configuration./
<Processor> - /Specify settings for processor./
Processor - /A dummy directive for backwards compatibility/
ServerEnvironment - /Specify the server environment for this virtual
host./
MultiplexerChroot - /Specify the multiplexer chroot path for
multiplexer/
Best regards
Michal Kumzak
Dne 20.1.2011 13:25, Taavi Sannik napsal(a):
Hello!
On 20.01.2011 2:23, Hannes Landeholm wrote:
Instead, I think this should be
implemented by a nice level setting which should be supported by all
kernels. The nice level basically sets the priority of the threads, so
if one environment is running with a lower nice level, it will get
more CPU time if it currently competing with another environment that
has a higher nice level. This is basic CPU time resource management
and prevents idle cycles.
Peruser has this already. Just use NiceLevel <level> in your processor
configuration.Do note that the nice level is more for prioritizing
load rather than blocking rogue workers.
You can also use kernel cgroups to monitor and limit cpu/memory. There
is also the PAM patch mentioned here previously (I'm not sure if
anyone has modified it to work with the latest peruser).
_______________________________________________
Peruser mailing list
[email protected]
http://www.telana.com/mailman/listinfo/peruser
