From: Sumit Sahu <[EMAIL PROTECTED]>
> Thanks for replying. Trimming the PATH is the last resort. I wanted
> to know if there is a cleaner way of doing things. Actually the PATH
> is indeed needed. I can trim it and then restore it at the end of the
> perl script (the problematic script that is ) because things
> downstream in our applications have a dependency on the PATH so cant
> risk fiddling with it.
I think there must be something wrong with your setup, but anyway.
You may trim the PATH just for the Perl script and the processes
started by that script. If you change the $ENV{PATH} it only affects
the stuff started by the script, nothing more, and you do not have to
restore anything.
Jenda
===== [EMAIL PROTECTED] === http://Jenda.Krynicky.cz =====
When it comes to wine, women and song, wizards are allowed
to get drunk and croon as much as they like.
-- Terry Pratchett in Sourcery
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
