Re: Strange results in modperl and Apache

in reply to Strange results in modperl and Apache

Could it be that one (or more) of the Apache's child processes didn't update its cache the last time the code changed? You could try restarting Apache (if you can, that is).

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

Note: All code is untested, unless otherwise stated

Comment on Re: Strange results in modperl and Apache

Replies are listed 'Best First'.
Re: Re: Strange results in modperl and Apache by Mr_Person (Hermit) on May 02, 2003 at 17:23 UTC
You can find more information about Apache's caching of your code (and how to fix problems caused by it) in the Reloading Modules and Required Files section of the mod_perl porting documentation.	[reply]
Re: Re: Strange results in modperl and Apache by pcouderc (Monk) on May 03, 2003 at 06:39 UTC
I can and I did. But my code does not change. it works... except when it does not!	[reply]

In Section Seekers of Perl Wisdom