Run shell script (with parameters) on Windows command line via Plink

You misunderstand how the -m switch works.

It is just a way to make plink load the commands to send to the server from a local file.

The file is NOT uploaded and executed on the remote server (with arguments).

It's contents is read locally and sent to the server and executed there as if you typed it on a (remote) command line. You cannot give it arguments.

A workaround is to generate the file on the fly locally before running plink from a batch file (say run.bat):

echo echo %1 > script.tmp
plink.exe -ssh username@host -pw gbG32s4D/ -m script.tmp

Then run the batch file with the argument:

run.bat 5

The above will make the script execute echo 5 on the server.

If the script is complex, instead of assembling it locally, have it ready on the server (as @MarcelKuiper suggested) and execute just the script via Plink.

plink.exe -ssh username@host -pw gbG32s4D/ "./myscript.sh %1"

In this case, as we execute just one command, you can pass it on Plink command line, including the arguments. You do not have to use the -m switch with a (temporary) file.

I triggered the Shell script in "commands.txt" from Plink which worked for me like a charm with below method I tried:

• You can define your script as an one liner using && in a file (I defined in one liner)
• You need to run your command in <

Note: Use first EOF in quote like <<'EOF' but not the last one. Else you will see you code will behave weirdly. Please see below.

Example:

sudo -i <<'EOF'
<your script here>
EOF

Then, finally run it using Plink:

plink -ssh username@hostname -pw password -m commands.txt