i use it in production and i am happy with the solution

On Wed, 14 Apr 2010 13:53:26 +0200, "Primož Barbo @ G-SERVER d.o.o."
<[email protected]> wrote:
> Because it says that it is not for comercial or production mode ready
> 
> On 14.4.2010 13:51, [email protected] wrote:
>> safe to use...
>>
>> On Wed, 14 Apr 2010 09:28:24 +0200, "Primož Barbo @ G-SERVER d.o.o."
>> <[email protected]>  wrote:
>>    
>>> Tell me something averyone. I have web hosting for few 1000 users and
is
>>>      
>>    
>>> this safe to use or not ?
>>>
>>>
>>>
>>> On 14.4.2010 7:34, [email protected] wrote:
>>>      
>>>> hi jordan,
>>>>
>>>> workaround: ignore it or pipe the output to /dev/null.
>>>>
>>>> @developers: would it be possible in the range of a MPM to overide
>>>>        
>> apache
>>    
>>>> default error handling? so lets say chroot is activated, apache will
>>>> check
>>>> if the complete chroot path is ok?
>>>>
>>>> On Wed, 14 Apr 2010 11:21:00 +0800, Jordan
Tomkinson<[email protected]>
>>>> wrote:
>>>>
>>>>        
>>>>> Hi,
>>>>>
>>>>> using 0.4rc1 with chroot, apache gives me a warning that the virtual
>>>>> hosts DocumentRoot does not exist.
>>>>>
>>>>> <Processor test1>
>>>>>     User user1
>>>>>     Group group1
>>>>>     Chroot /home/jail
>>>>> </Processor>
>>>>>
>>>>> <VirtualHost *:80>
>>>>>       <IfModule peruser.c>
>>>>>           ServerEnvironment test1
>>>>>       </IfModule>
>>>>>       DocumentRoot /var/www/test1/html
>>>>>       ServerName test1
>>>>> </VirtualHost
>>>>>
>>>>> So after chroot the DocumentRoot actually becomes
>>>>> /home/jail/var/www/test1/html and everything works fine (documents
are
>>>>> served by apache etc..)
>>>>> but when I start/restart apache it looks for /var/www/test1/html
>>>>> outside the chroot and warns that it does not exist.
>>>>> _______________________________________________
>>>>> Peruser mailing list
>>>>> [email protected]
>>>>> http://www.telana.com/mailman/listinfo/peruser
>>>>>
>>>>>          
>>>> _______________________________________________
>>>> Peruser mailing list
>>>> [email protected]
>>>> http://www.telana.com/mailman/listinfo/peruser
>>>>
>>>>        
>> _______________________________________________
>> Peruser mailing list
>> [email protected]
>> http://www.telana.com/mailman/listinfo/peruser
>>
_______________________________________________
Peruser mailing list
[email protected]
http://www.telana.com/mailman/listinfo/peruser

Reply via email to