On Thursday, August 19, 2010 18:24:15 Mark Risher wrote:
> > The only thing where mod_perl may stay in the way here is if you use
> > somehow a
> >
> > different interpreter for child_init than for handler. Do you use a
> > threaded MPM, e.g. windows? Do you use the +Parent PerlOption in a
> > V
Mark Risher wrote:
...
[mr] I'm getting different addresses, which illustrates the problem
2010/08/19 18:13:37 child_init &sticky = SCALAR(0x220ea748)
2010/08/19 18:13:37 child_init sticky (pre) = 0
2010/08/19 18:13:37 child_init sticky (post) = 1
...
2010/08/19 18:13:48 handler sticky (should
Thank you for the suggestions. Unfortunately, I am still not able to make
it work.
Spurred by your advice, I examined my apache2.conf config. Here it is:
PerlSwitches -I/mnt/hgfs/src/api# the path where my modules live
PerlModule StartupLog
PerlChildInitHandler StartupLog::child_init
Se
On Thursday, August 19, 2010 09:12:41 Mark Risher wrote:
> I am trying to load a configuration file into a hash during my
> PerlChildInitHandler and then access the values from PerlResponseHandler.
> However, even though the process number is the same, it seems that
> variables changed during th
Hi, all:
I am trying to load a configuration file into a hash during my
PerlChildInitHandler and then access the values from PerlResponseHandler.
However, even though the process number is the same, it seems that variables
changed during the child_init() call revert back to their default values