comment on

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.

In reply to Re^2: perl lost its modules! by garry
in thread perl lost its modules! by seandarcy

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks