By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,276 Members | 2,063 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,276 IT Pros & Developers. It's quick & easy.

Perl Help - Windows Perl script accessing a Unix perl Script

P: n/a
Hello,

I have two different scripts that do pretty much the same thing. The main
perl script is on Windows. It runs and in the middle of it, it then calls
out another perl script that then should run on a Unix box I have. Both
scripts run ok, except for the part when Windows try's to call out the
Unix script. I have it set up where the Unix is mapped through a drive
letter and can drop stuff into the Unix box. It is going through another
server to do that. So I can see the script and drop files into the Unix box
but just can't figure out why perl will not call out the script. When I call
out the perl script through the command line of windows I get " specified
path not found", even though I'm in that directory.

Has any one done anything like this that would be willing to either help me
or point me in the right direction to do research on it. Thanks

-Dale
Jul 19 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On Mon, 29 Sep 2003 03:05:05 GMT
"dpackwood" <dp*******@earthlink.net> wrote:
I have two different scripts that do pretty much the same thing. The
main perl script is on Windows. It runs and in the middle of it, it
then calls out another perl script that then should run on a Unix
box I have. Both scripts run ok, except for the part when Windows
try's to call out the Unix script. I have it set up where the Unix
is mapped through a drive letter and can drop stuff into the Unix
box. It is going through another server to do that. So I can see the
script and drop files into the Unix box but just can't figure out
why perl will not call out the script. When I call out the perl
script through the command line of windows I get " specified path
not found", even though I'm in that directory.

Has any one done anything like this that would be willing to either
help me or point me in the right direction to do research on it.
Thanks


Code would be helpful :-)

So "pointers" to help you solve your own issue:
1) #!/usr/bin/perl -w on the first line :-)
2) use strict on the second line :-)
3) use diagnostics on the third line :-)

HTH

--
Jim

Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.

a fortune quote ...
There is a green, multi-legged creature crawling on your
shoulder.
Jul 19 '05 #2

P: n/a
In article <Bj*****************@newsread4.news.pas.earthlink. net>,
dpackwood <dp*******@earthlink.net> wrote:
Hello,

I have two different scripts that do pretty much the same thing. The main
perl script is on Windows. It runs and in the middle of it, it then calls
out another perl script that then should run on a Unix box I have. Both
scripts run ok, except for the part when Windows try's to call out the
Unix script. I have it set up where the Unix is mapped through a drive
letter and can drop stuff into the Unix box. It is going through another
server to do that. So I can see the script and drop files into the Unix box
but just can't figure out why perl will not call out the script. When I call
out the perl script through the command line of windows I get " specified
path not found", even though I'm in that directory.

Has any one done anything like this that would be willing to either help me
or point me in the right direction to do research on it. Thanks

-Dale


What do you mean by "call out" (this is where posting code would help)?
Are you trying to get the Unix box to execute its own script? For that,
you need the equivalent of ssh or rsh or the like. If you are just
calling the second script with backticks or the system call, the perl
interpreter on the Windows machine will attempt to fork a subprocess to
execute the script on the _Windows_ system. If the first line of the
Unix script contains the path to the perl program on the Unix box and
that path is different from the path to the Windows perl executable, as
it is likely to be, you will get the message you are seeing.
Jul 19 '05 #3

P: n/a
Thank you to everyone who replied. I think I have found the answer. If not I
will let you know. Thanks again
"dpackwood" <dp*******@earthlink.net> wrote in message
news:Bj*****************@newsread4.news.pas.earthl ink.net...
Hello,

I have two different scripts that do pretty much the same thing. The main
perl script is on Windows. It runs and in the middle of it, it then calls
out another perl script that then should run on a Unix box I have. Both
scripts run ok, except for the part when Windows try's to call out the
Unix script. I have it set up where the Unix is mapped through a drive
letter and can drop stuff into the Unix box. It is going through another
server to do that. So I can see the script and drop files into the Unix box but just can't figure out why perl will not call out the script. When I call out the perl script through the command line of windows I get " specified
path not found", even though I'm in that directory.

Has any one done anything like this that would be willing to either help me or point me in the right direction to do research on it. Thanks

-Dale

Jul 19 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.