The normal way I deal with this situation is to first install cygwin, a linux environment inside windows.
Then, I'd get rsh installed via cygwin. If you need encryption, use ssh. rsh is less secure, but easier to set up. access is regulated by hosts files.
If it's possible to alter the perl script to emit the report to standard output, you can get away with a cool unix technique. The rsh command pipes the output of the command to your screen, so you can save it to a file with >.
rsh /usr/bin/perl the_script.pl > output_file
If you can't modify that script, an alternative is to write a wrapper script that first, runs the perl script to produce the report, and then reads the report to the output:
#! /bin/sh
perl the_script.pl
cat report.txt
Then, from your server, call the wrapper via rsh
rsh wrapper > output_file
Voila, no need for ftp, or even file copying.
Main Topics
Browse All Topics





by: fridomPosted on 2006-12-19 at 22:33:40ID: 18171676
IMHO you should ope for ssh. For windows you could use putty e.g: .org.uk/~s gtatham/pu tty/ downlo ad.html
emote_host perl_script
emote_host :/path_to_ the_output .
http://www.chiark.greenend
for executing a command on the "linux" side simply use
plink
plinkg user_name_at_remote_host@r
for copying the files you use
pscp
pscp user_name_at_remote_host@r
Regards
Friedrich