Yes,
Because in my error messages it clearly says it can't find the modules
in @INC. Then it shows all the paths in @INC and my custom lib isn't set
there, instead, @INC is at it's original state.
Christiaan Kras
Perrin Harkins schreef:
On 7/6/07, Christiaan Kras <[EMAIL PROTECTED]> wrote:
I'm 100% sure it happens in the modules that use lazy loading
(eval(require "module.pm")). Somehow @INC gets reset.
Are you sure @INC is getting reset? Sometimes people have this
problem because the user that apache runs as (usually "nobody")
doesn't have permissions to access the directories in @INC. At
startup, they get loaded as root, so this isn't an issue at that time.
- Perrin
