Re: modperl PerlAuthenHandler script persistence

In both apache 1 and apache 2, each request may be handled by a different process, so you can't just keep things in a hash in memory if you want them to be global. The exception to this is if you were using apache 1 on Windows. There it only used one thread before and now uses multiple. Were you running it on Windows?

Comment on Re: modperl PerlAuthenHandler script persistence

Replies are listed 'Best First'.
Re^2: modperl PerlAuthenHandler script persistence by SirBones (Friar) on Mar 29, 2006 at 02:25 UTC
No, sorry, I forgot to mention the OS. It's Linux in both cases. The mystery deepens. Do you think the aberrant behavior is actually with my older server, and the new one is WAD? "This bounty hunter is my kind of scum: Fearless and inventive." --J.T. Hutt	[reply]
Re^3: modperl PerlAuthenHandler script persistence by Anonymous Monk on Mar 29, 2006 at 11:55 UTC
Limiting the number of children to 1 would explain old behaviour	[reply]
Re^4: modperl PerlAuthenHandler script persistence by SirBones (Friar) on Mar 29, 2006 at 15:49 UTC
>Limiting the number of children to 1 would explain old behaviour Do you mean the number of Apache child processes? Or is this a modperl setting? I inspected the information under `perl-status`, but couldn't find anything about the number of children. "This bounty hunter is my kind of scum: Fearless and inventive." --J.T. Hutt	[reply] [d/l]