Re^3: Can't locate Modules/test.pm in @INC

~~Likely taint mode was switched on because you're running with setuid or setgid. You probably do not want the current directory to be in @INC if that's the case.~~

Forget that. Anyway, normal scripts never have cwd set to the location of the script. Apache does it for CGI scripts but you should probably not rely on that. See FindBin.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re^3: Can't locate Modules/test.pm in @INC

Replies are listed 'Best First'.
Re^4: Can't locate Modules/test.pm in @INC by techcode (Hermit) on Feb 23, 2007 at 10:34 UTC
Wow - I guess you learn something new each day. Beside being able to swear that I read somewhere that cwd is automaticly set to location where script is running. I never had an problem with that in the past ~ 5 years of working with Perl. Here is the source Changing the Working Directory which I found out yesterday - but I got it from other places in the past ... EDIT: During development and testing I used -T option. First thought was that it's the thing causing the problem on the server - obviosly it isn't. Have you tried freelancing? Check out Scriptlance - I work there. For more info about Scriptlance and freelancing in general check out my home node.	[reply]
Re^5: Can't locate Modules/test.pm in @INC by Joost (Canon) on Feb 23, 2007 at 14:13 UTC
Huh. that page is wrong. :-) At least it doesn't work like that if you run a script from the command line / shell script. Running from a shell does not change the cwd, because that would defeat the point of having a cwd in the first place. Some other environments do set the cwd; usually to the scrip's install dir, but that's normally because there isn't a logical cwd to begin with (i.e. in a CGI environment, or on windows, if you start a script by clicking on its icon) "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]