[ Jim Jagielski ]
> On Sep 27, 2006, at 9:13 AM, Kenneth Svee wrote:
>
>> [ Jim Jagielski ]
>>
>>> Kenneth Svee wrote:
I've ported the old config to Apache 2.2, and we're about 11
vhosts over the limit on the new build. The 1.3.37-server works.
The 2.2.3-server starts if i comm
The SLACK_LINE stuff was about preserving low-numbered fds for use by
stdio because of the Solaris 8-bit fd limit with stdio. It's not in 2.x
because 2.x doesn't use stdio for logging.
If you're hitting fd limits in 2.2 it is only because of kernel fd
limits which need fixing with limit/ulimit
On Sep 27, 2006, at 9:13 AM, Kenneth Svee wrote:
[ Jim Jagielski ]
Kenneth Svee wrote:
I've ported the old config to Apache 2.2, and we're about 11 vhosts
over the limit on the new build. The 1.3.37-server works. The
2.2.3-server starts if i comment out 11 vhosts. With 10 vhosts
commented o
[ Jim Jagielski ]
> Kenneth Svee wrote:
>>
>> I've ported the old config to Apache 2.2, and we're about 11 vhosts
>> over the limit on the new build. The 1.3.37-server works. The
>> 2.2.3-server starts if i comment out 11 vhosts. With 10 vhosts
>> commented out, the server dumps this to the "glob
Kenneth Svee wrote:
>
> I've ported the old config to Apache 2.2, and we're about 11 vhosts
> over the limit on the new build. The 1.3.37-server works. The
> 2.2.3-server starts if i comment out 11 vhosts. With 10 vhosts
> commented out, the server dumps this to the "global" error_log, and
> dies:
Hi.
We have an older Apache 1.3 server with 130-ish VirtualHosts on
Solaris 8. This runs PHP and mod_perl with lots of dependencies. We've
built Apache 2.2.3 with the same basic functionality (PHP4.4.4,
mod_perl2.0.2). On this server each vhost has it's own access_log and
error_log, and we want to
