in reply to Re^3: back tick to do ssh
in thread back tick to do ssh

Unfortunately, our system's perl is pretty old,
This is perl, version 5.005_03 built for sun4-solaris Copyright 1987-1999, Larry Wall Perl may be copied only under the terms of either the Artistic License + or the GNU General Public License, which may be found in the Perl 5.0 source +kit. Complete documentation for Perl, including FAQ lists, should be found +on this system using `man perl' or `perldoc perl'. If you have access to + the Internet, point your browser at http://www.perl.com/, the Perl Home Pa +ge.
and I can't use the module that I wanted to use
userX@myserver ~/script> perl -c scriptX.pl Weak references are not implemented in the version of perl at /home/us +erX/script/pm/Net-SSH-Perl-1.30/lib/Net/SSH/Perl/Packet.pm line 22 BEGIN failed--compilation aborted at /home/userX/script/pm/Net-SSH-Per +l-1.30/lib/Net/SSH/Perl/Packet.pm line 22. BEGIN failed--compilation aborted at /home/userX/script/pm/Net-SSH-Per +l-1.30/lib/Net/SSH/Perl.pm line 6.
I will try to run stuff from remote by other script and just extract it

Replies are listed 'Best First'.
Re^5: back tick to do ssh
by graff (Chancellor) on Dec 31, 2007 at 08:21 UTC
    I feel your pain (there are still some old suns where I work, still running an ancient version of perl). Here's an idea that might keep things coherent for you. if the stuff that needs to be done on the remote box is always the same, there's no problem: put a shell or perl script there to do the job, and run that from your local machine via ssh in backticks.

    But if the remote actions need to vary for whatever reason, your local perl script could probably build the necessary script that would need to run on the remote machine, save it to a local file, "scp" it to the remote box, and then run it via ssh in backticks. (But usually you can set it up so only one version of the remote script is needed, and it uses command-line args to handle the necessary variations.)