Solved Resolving a variable

[balanga]

I'm trying to run a program on a remote system over ssh using something like:-

ssh $REMOTE 'sh -x $PROG'

where $REMOTE is the IP address of the remote host, and $PROG is the program I want to run.

Unfortunately I can't get $PROG to resolve. The command works if PROG is hard coded.

The program is copied to the remote host successfully using:-

scp -p 22 $PROG root@$REMOTE:/root/$PROG

I'm trying to copy a program created by script, and run it on the remote. The copy works but I can't run it unless I hard code the program name. How do I resolve the variable $PROG when I want to run it?

 

[elgrande]

I‘d guess you need double quotes instead of single quotes.

 

[Erichans]

I suggest you have a look at POSIX Shell-strong versus weak quoting & UNIX SHELL Quote Tutorial, study them and search them when you have them open at all times when you do shell commands/scripting.

 

[balanga]

Many thanks, that worked.

 

[balanga]

This is what I should have used.

ssh $REMOTE "sh -x $PROG"

 

[SirDice]

If ${PROG} points to an executable and it has a proper shebang line, you don't have to start it with sh(1).

 

[balanga]

How do I get #!/bin/sh into a heredoc?

 

[SirDice]

dice@fbsd-test:~/test % ll
total 1
-rwxr-xr-x  1 dice dice 76 May 29 11:48 heredoc.sh*
dice@fbsd-test:~/test % cat heredoc.sh
#!/bin/sh


cat <<HERE  > somefile.sh
#!/bin/sh

echo "Hello World!"
HERE


dice@fbsd-test:~/test % ./heredoc.sh
dice@fbsd-test:~/test % cat somefile.sh
#!/bin/sh

echo "Hello World!"

 

[balanga]

How do I get #!/bin/sh into a heredoc?

I just figured it out - easier than I thought. I half expected that some characters would need to be escaped...

 

[balanga]

If ${PROG} points to an executable and it has a proper shebang line, you don't have to start it with sh(1).

I needed to change

ssh $REMOTE "sh -x $PROG"

to
ssh $REMOTE "~/$PROG"

to make it work

 

[SirDice]

Yes, the same with any executable, current working directory is never part of PATH.