You say "some of my perl scripts" throw out the error. At what point do they throw the error, are they calling other scripts? What is different between those that work and those that do not?
Is "Can't open perl script" the error message, the whole error message, and nothing but the error message? Are you sure that is not comming from (say) a system command or qx? | [reply] |
Can it be that the upgrade touched some policy file indicating which interpreter can be run from the she-bang line? thinking /etc/shells and possible relatives here.
cheers
--stephan
| [reply] |
I would say it has to do with permissions. Can you check if you have read and execute permission for those perl scripts ?
LuCa
| [reply] |
permissions were right.
I finally could make some scripts work by adding -U flag
and some scripts were include a file
for some reason #!/usr/bin/perl -I/<pathtomodule> works
while #!/usr/bin/perl -I <pathto module> does not
Thanks to all monks for their prompt and quick responses !!
| [reply] |
| [reply] |
AIX 5.2
I checked the path , permissions etc.
which perl shows perl in /usr/bin/perl which the script points to.
I had to modify PERL5LIB variable some other scripts work.
But few scripts seem to work only by adding perl in the front. Since there are lot of scripts .
The same script works perfectly on another box with the same environment.
| [reply] |
| [reply] |
"was upgraded" doesn't sound like sufficient information to formulate a solution. And it seems inconceivable that changing the O/S version should alone have such an impact. Something else has happened to coincide with the upgrade or possibly as part of some arcane plan associated with the upgrade and you need to find out what - otherwise we are just guessing!
__________________________________________________________________________________
^M Free your mind!
| [reply] |