As Mladen hints, this was just 'the way it was done' since the Apache 1.3
MPM was first created. I began to set up more of the structures for having
parallel running httpd's and Mladen took this one step further with his
winxp mpm, but the bottom line is that resource sharing just doesn't work
is this still compatible with the current trunk?
If so maybe it can be reactivated for trunk and 2.2?
From what i gather from the info it seems interesting enough.
On 11/20/06, Mladen Turk <[EMAIL PROTECTED]> wrote:
Issac Goldstand wrote:
>
> I don't think that the problem is mod_perl, as muc
Issac Goldstand wrote:
> CC-ing to [EMAIL PROTECTED] in the hopes that someone
> (**cough**wrowe?**cough**)
> might shed some deeper insight into why things were/are done the way
> they are, and what, if anything, would be needed to be done to make
> things better.
>
> I don't think that the prob
Philip M. Gollucci wrote:
> William A. Rowe, Jr. wrote:
>> Keep in mind, using the official build of httpd you have .pdb debug
>> files that can be downloaded that exactly match the .exe/.dll's/.so's
>> that we ship. That means you can -debug- these segfaults.
> Am I able to make these from UNIX ?
Issac Goldstand wrote:
I don't think that the problem is mod_perl, as much as the winnt MPM in
Apache2. The bottom line is that if anything goes wrong, you need the
singleton child process to recycle itself, and very often in the case of
mod_perl that can take a long time.
There is experim
