Re: perl lost its modules!

No idea, but maybe changing file permissions to 755 or possibly even 775 for every file in the INC hierarchy might solve the issue.

Comment on Re: perl lost its modules!

Replies are listed 'Best First'.
Re^2: perl lost its modules! by garry (Novice) on Apr 02, 2014 at 01:27 UTC
That's a bad idea. You shouldn't change the permissions on files in /usr directories except for the ones that you (the system administrator) own like in /usr/local. Furthermore, running a command like `chmod -R` is especially dangerous, if you do not understand what you are doing. The `*.pm` files in /usr are supposed to have 0644 permissions. They should not be set with execute. They are not executable files, after all. Having said all that, this particular change is most likely benign. But you should never change files in the /usr directory except your own. These files and their permissions are managed by the system and rpm(8) in the OP's case. Run the command `rpm -V perl` to see all the "damage" now.	[reply] [d/l] [select]
Re^2: perl lost its modules! by seandarcy (Initiate) on Apr 01, 2014 at 23:30 UTC
`chmod -R 775 /usr/share/perl5` no success. And I can already read the modules: for instance I can cat strict.pm. It doesn't appear to be a linux permissions issue.	[reply] [d/l]