in reply to Re^7: Custom module is present but not read by Apache (?)
in thread Custom module is present but not read by Apache (?)

Ok, it is, because this path is not in the new server's INC. Can I install the Error.pm module in anothe path? When I do it through CPAN, I think it puts it under /root/perl5, which is not part of @INC

Replies are listed 'Best First'.
Re^9: Custom module is present but not read by Apache (?)
by tobyink (Canon) on Dec 10, 2019 at 13:41 UTC

    You probably don't want the contents of /root to be visible to Apache. I would suggest installing Error.pm somewhere sensible instead of making /root world-readable.

      Yes yes, I fully agree, I am just asking how can I "force" the installation of the Error.pm under one of the common directories, e.g.  /usr/local/lib64/perl5
        Ok, I got it now. I installed it with yum and it works. A quick (hopefully last) question if I may: now it complaints that more packages are not visible through @INC (again, installed with CPAN). An example is HTML::Entities, which I could find with CPAN but not to install with yum. Is there a place where I can look for these things?
Re^9: Custom module is present but not read by Apache (?)
by Corion (Patriarch) on Dec 10, 2019 at 13:46 UTC

    Consider using the system package manager to install the module, or local::lib.

    Avoid "installing" modules as root, as that rarely does what you want.