William A. Rowe, Jr. wrote:
> Ivan Barrera A. wrote:
>> William A. Rowe, Jr. wrote:
>>> No. Run multiple instances of httpd against different IP addresses.
>>>
>>> There's no way to decide about accepting per-named-host.
>> There are some third party modules that can do it.
>> I only wrote for apa
Ivan Barrera A. wrote:
> William A. Rowe, Jr. wrote:
>> No. Run multiple instances of httpd against different IP addresses.
>>
>> There's no way to decide about accepting per-named-host.
>
> There are some third party modules that can do it.
> I only wrote for apache 2, but there is equivalents i
William A. Rowe, Jr. wrote:
> No. Run multiple instances of httpd against different IP addresses.
>
> There's no way to decide about accepting per-named-host.
There are some third party modules that can do it.
I only wrote for apache 2, but there is equivalents in apache 1.
>
> Chuck Rock wro
No. Run multiple instances of httpd against different IP addresses.
There's no way to decide about accepting per-named-host.
Chuck Rock wrote:
> I have a site that uses up all my apache slots occasionally. This leaves all
> the other sites on that server unable to access.
>
> Does anyone know
I have a site that uses up all my apache slots occasionally. This leaves all
the other sites on that server unable to access.
Does anyone know if there's a way in the Apache config file to limit a site to
say 100 simultaneous connections and that way leaves the rest available for
the other site
