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

Replies are listed 'Best First'.
Re^8: Custom module is present but not read by Apache (?) by Anonymous Monk on Dec 10, 2019 at 13:39 UTC
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	[reply] [d/l]
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. toby döt ink	[reply] [d/l] [select]
Re^10: Custom module is present but not read by Apache (?) by Anonymous Monk on Dec 10, 2019 at 13:45 UTC
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`	[reply] [d/l]
Re^11: Custom module is present but not read by Apache (?) by Anonymous Monk on Dec 10, 2019 at 13:57 UTC
Re^12: Custom module is present but not read by Apache (?) by Corion (Patriarch) on Dec 10, 2019 at 14:01 UTC
Re^12: Custom module is present but not read by Apache (?) by tobyink (Canon) on Dec 10, 2019 at 15:46 UTC
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.	[reply]