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

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

Comment on Re^9: Custom module is present but not read by Apache (?) Select or Download Code

Replies are listed 'Best First'.
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
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?	[reply] [d/l]
Re^12: Custom module is present but not read by Apache (?) by Corion (Patriarch) on Dec 10, 2019 at 14:01 UTC
Consider asking your system administrator where/how they want such modules installed. Also, local::lib is a good way to set up modules as (and for) a given user. That user would install the modules into a local directory and you could then give the Apache user read permissions to that directory.	[reply]
Re^12: Custom module is present but not read by Apache (?) by tobyink (Canon) on Dec 10, 2019 at 15:46 UTC
I don't think you mentioned which distribution you're using, but try the `perl-HTML-Parser` package. toby döt ink	[reply] [d/l]