Re: run perl script with cmd line in shell

[MidLifeXis]

#!usr/binn/csh
 ssh user@server perl < script.pl $cmdlinArgtoscrpt

It appears that you are asking to have a perl command run the local script script.pl on server with the parameters $cmdlinArgtoscrpt. Is this correct?

Update: "Hello. My name is MidLifeXis, and I am a complexaholic." See Re^2: run perl script with cmd line in shell for a better solution.

I see various solutions to this, with different difficulties:

• Share the script to the remote machine and execute it from that shared location.
• Copy the script.pl to the remote machine and run it from there. There are potential race conditions between the copy / execute and the execute / cleanup.
• Embed the command line arguments into the top of your script.pl, perhaps as you are sending it across the wire to perl. This would require some pre-processing of the script and some assumptions of where you can embed the code - if I were to do it this way, I would probably have a token of some sort in the script that I would replace with my parameters.
• Run the command remotely using the -e or -E flag to perl, and embedding the script on the remote command invocation. This would be my last choice for something that is any more complex than dead simple unless I could ensure that quotes were properly escaped, newlines handled, length of the command line accounted for, and so on.

Update: I do not mean to imply that these are the only solutions -- there may well be something much more elegant, robust, and maintainable than any idea proposed above.

[Anonymous Monk]

Is there a reason why something like ssh user@server perl - $cmdlinArgtoscrpt < script.pl would not work?

use Data::Dumper;
print Dumper(\@ARGV);

# testing:
$ ssh someserver perl - aoeu snth < localscript.pl
$VAR1 = [
          'aoeu',
          'snth'
        ];

[Anonymous Monk]

Just wanted to add that due to the way ssh executes commands, you may need to shell-quote your command line arguments twice if they have _any_ odd characters:

% ssh someserver perl - "foo bar" < localscript.pl 
$VAR1 = [
          'foo',
          'bar'
        ];
% ssh someserver perl - "foo (bar)" < localscript.pl 
bash: -c: line 0: syntax error near unexpected token `('
bash: -c: line 0: `perl - foo (bar)'

% ssh someserver perl - '"foo (bar)"' < localscript.pl 
$VAR1 = [
          'foo (bar)'
        ];

[icoder]

This Solution worked well

[Anonymous Monk]

-->>ssh user@server perl - $cmdlinArgtoscrpt < script.pl Worked well, thanks

[Anonymous Monk]

Hi MidLifeXis, Thanks.Correct Exactely.

1)Share the script to the remote machine and execute it from that shared location.

--> I can't do that. may be the script given as a patch,that can't put into server that is dynamic

2)Copy the script.pl to the remote machine and run it from there. There are potential race conditions between the copy / execute and the execute /

--> Same above said reason, i cant do that

3)Embed the command line arguments into the top of your script.pl, perhaps as you are sending it across the wire to perl. This would require some pre-processing of the script and some assumptions of where you can embed the code - if I were to do it this way, I would probably have a token of some sort in the script that I would replace with my parameters

--> The cmd line argumetns are also dynamic in nature..but i dont understand this entire statment correctely. can you give an example ?

4)Run the command remotely using the -e or -E flag to perl, and embedding the script on the remote command invocation. This would be my last choice for something that is any more complex than dead simple unless I could ensure that quotes were properly escaped, newlines handled, length of the command line accounted for, and so on. --> I think this will work out may be..i will give it a try and also i am trying with sed cmd as well

[MidLifeXis]

3)Embed the command line arguments into the top of your script.pl, perhaps as you are sending it across the wire to perl. This would require some pre-processing of the script and some assumptions of where you can embed the code - if I were to do it this way, I would probably have a token of some sort in the script that I would replace with my parameters --> The cmd line argumetns are also dynamic in nature..but i dont understand this entire statment correctely. can you give an example ?

In your script you could have something like:

# Earlier stuff in the script...

# Fill in the arguments if running remotely
@ARGV ||= qw(%%REPLACEDTOKEN%%);
# ... and back it out if @ARGV should really be empty
@ARGV =   () if $ARGV[0] eq "\%\%REPLACEDTOKEN\%\%";

# Rest of your script

At this point, you would use something locally to replace '%%REPLACEDTOKEN%%' with your parameters, and pipe that to a perl call on the remote machine.
sed -e .... < script.pl | ssh user@remote perl

I still have concerns that this is the most robust solution to your problem.

Do your scripts use any temporary files? If so, I would seriously reconsider your answer to number 2. If you can write temp files, you can also write a temporary perl script.