Re^4: Should I upgrade from mod_perl 1.0 to 2.0? and if so, how?

Replies are listed 'Best First'.
Re^5: Should I upgrade from mod_perl 1.0 to 2.0? and if so, how? by Corion (Patriarch) on Feb 17, 2009 at 15:02 UTC
Again, looking at the Apache::DBI source code, it seems that `Apache.pm` should be there once you're running under mod_perl (1), so, the circumstances point to you not running under mod_perl.	[reply] [d/l]
Re^6: Should I upgrade from mod_perl 1.0 to 2.0? and if so, how? by MashMashy (Sexton) on Feb 17, 2009 at 15:03 UTC
that gateway line ticks over, though, so there's an indication that I am. what could I do to check if I am or not?	[reply]
Re^7: Should I upgrade from mod_perl 1.0 to 2.0? and if so, how? by Corion (Patriarch) on Feb 17, 2009 at 15:07 UTC
Maybe consult with your machine administrator. As I already told you, if `Apache.pm` is not there, chances are, you're not running under mod_perl. I don't know what else to tell you. Maybe read the Apache or mod_perl documentation about how to more clearly divine whether you're really running under mod_perl or not.	[reply] [d/l]
Re^6: Should I upgrade from mod_perl 1.0 to 2.0? and if so, how? by MashMashy (Sexton) on Feb 17, 2009 at 15:09 UTC
I also see this: in that info page: MOD_PERL 1.0 Note that this module needs mod_perl-1.08 or higher, apache_1.3.0 or higher and that mod_perl needs to be configured with the appropriate call-back hooks: PERL_CHILD_INIT=1 PERL_STACKED_HANDLERS=1 How can I check if those hooks are implemented? could this error be caused by that?	[reply]