Server Settings?

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

I have changed to a new server provider and my scripts that previously ran ok on the former server now bring back 'No such file or directory' error. On adding warnings the script is run but reports a number of problems. To save rewriting all the scripts to fix these problems (and they are long and many) I was wondering if there was some setting that could be changed to make perl/server less strict so it would let them run as before?

Thanks very much for any help
Cheers
Chris

Comment on Server Settings?

Replies are listed 'Best First'.
Re: Server Settings? by phydeauxarff (Priest) on Apr 18, 2003 at 02:21 UTC
Without seeing the errors we are just shooting arrows into the air, but some things to check are..... Is perl in the same location and accessible by your scripts on the new ISP as it was on the old? Are your scripts depending on any modules that don't exist on the new service? Have you spoken with tech support at your new ISP? Most credible ISPs have good tech support or even FAQ's concerning their support of scripts on their services.	[reply]
Re: Server Settings? by hiseldl (Priest) on Apr 18, 2003 at 14:03 UTC
This sounds like your `#!/usr/bin/perl` line may need to be changed. Check where the perl executable is on your new system, and check the path in your scripts to make sure it is the same. On linux/solaris you can use `$ which perl` [download] and if this does not seem to fix the problem, try testing your scripts like this `$ perl -cw myscript.pl` [download] If you get a 'No such file or directory' error while trying that, then Perl is probably not installed on your host's system. :( HTH -- hiseldl What time is it? It's Camel Time!	[reply] [d/l] [select]
Re: Server Settings? by nothingmuch (Priest) on Apr 18, 2003 at 01:12 UTC
If there's something wrong perhaps it's better to find and fix, instead of ignoring? If you give us more info, such as what generated the error, source and all, the solution might be very simple... If you'd rather not, then at least more info about your environment (platform, server, etc) is mandatory, though I doubt such a solution will allow you to reap any results. -nuffin zz zZ Z Z #!perl	[reply]