Just wondering.
Since the files to be changed are preset to "644", this would imply they are readable, but not writable or executable ... so in essence, they cannot be modified by an external script, which is where the violation is coming in.
Maybe the "umask" command set to "000" would temporarily set all the files to "777", and then chmod can change them back to "755" or "705"
In reply to Re: When modules install in perl5
by cristofayre
in thread When modules install in perl5
by cristofayre
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |