[peruser] Some more questions about the peruser configuration
janno at kood.ee
Mon Apr 20 05:06:36 MDT 2009
Password 'peruser' doesn't seem to open any doors....
On 20.04.2009 13:54, Stefan Klingner wrote:
> thanks for your answer! :) hopefully the other questions will also find an
> answer. if anyone is interested in my current documentation about this
> stuff, you can read the stuff under
> currently it is protected, because it is still alpha state. The password is
> simply 'peruser'. You can leave a comment if you have some hints or
> criticism. thanks a million for the help!
> On Mon, 20 Apr 2009 13:40:40 +0300, Janno Sannik<janno at kood.ee> wrote:
>> Keepalive is supported and works. Use it.
>> On 2.04.2009 15:27, Stefan Klingner wrote:
>>> one more time I have some questions about peruser with dc2 patch.
>>> Is KeepAlive supportet correctly now, or should KeepAlive=off used
>>> Of course I would prefer KeepAlive=On with a KeepAliveTimeout=1!?
>>> How can I determine usefull values for the MinMultiplexers and
>>> MaxMultiplexers values which are limiting the multiplexer pool?
>>> How can I calculate MaxClients. What do you think about the following
>>> MaxClients ~ (RAM - size_all_other_processes)/(size_apache_process)
>>> metis:~# free -m
>>> total used free shared buffers
>>> Mem: 373 328 44 0 163
>>> -/+ buffers/cache: 98 274
>>> Swap: 400 0 399
>>> So MaxClients ~ 274/12 ~ 22...
>>> Why I have to set Chroot to / like here
>>> <Processor test>
>>> User test
>>> Group www
>>> Chroot /
>>> to get it up? Is the defined DocumentRoot of the VirtualHost used as
>>> dir? What ever... with this configuration chroot does not work like it
>>> should in my opinion. I should not be able to see system configurations
>>> an chrooted environment with simple php tools like eXtplorer.
>>> Thanks for your help!
>> Peruser mailing list
>> Peruser at telana.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Peruser