Programming

I've never heard of a shell which doesn't take -s. Even weird things like csh do it. But -- might be less common, though it's luckily optional.

If your shell doesn't take them, leave them out, they're optional.

What the double-dashes do is prevent the shell from interpreting arguments after it as flags like -f or what have you, which could change the behavior of the shell.

Unfortunately none of these fixes my issue. Actually the "-s" switch without the "--" worked for me with my direct (no sesu) command. Here is the working command.

Code:

ssh <targetserver> exec /usr/bin/ksh -s a b c << "EOF"
echo $1 $2 $3
EOF

However once I spice it up and introduce a sesu command into the mix it fails. This is the failing statement:

Code:

ssh <user>@<targetserver> /usr/seos/bin/sesu - <user> -c "/usr/bin/ksh" -s a b c << "EOF"
echo $1 $2 $3
EOF

so the difference is that it must need a different kind of call for the "-c" command switch for sesu I think.... any ideas?

---------- Post updated at 10:46 ---------- Previous update was at 10:40 ----------

NB have tried that with and without exec in addition to "-c"

Code:

ssh <user>@<targetserver> /usr/seos/bin/sesu - <user> -c "exec /usr/bin/ksh -s a b c" << "EOF"
echo $1 $2 $3
EOF

---------- Post updated at 11:03 ---------- Previous update was at 10:46 ----------

OK the "-c" on the sesu seems to remove the need to call "exec". However I'm guessing the "-s", which I intend as a switch on the ksh, is actually trying to be interpreted as part of the sesu..... tried using apostrophes as below but still not working... getting the error: "/bin/su: a: No such file or directory"

(NB being in Korn first to run this code)

Code:

ssh <user>@<targetserver> /usr/seos/bin/sesu - <user> -c '/usr/bin/ksh -s a' << "EOF"
echo $1
EOF

---------- Post updated at 14:29 ---------- Previous update was at 11:03 ----------

OK almost cracked I think - need apostrophes around the whole passed command - E.g.

Code:

ssh <user>@<targetserver> '/usr/seos/bin/sesu - <user> -c "/usr/bin/ksh -s a"' << "EOF"
echo $1
EOF

however..... I find now that I cannot dynamically generate this command. If I pass that whole command string:

Code:

'/usr/seos/bin/sesu - <user> -c "/usr/bin/ksh -s a"'

as a variable $command. Then it doesn't work... if I run it without variable substitution it does work... cannot figure out why - the var does include the speech marks and apostrophes - if you echo it, then it comes out exactly as the command that works when you run it all in one line....

The error btw is as follows:

Code:

sh: /usr/seos/bin/sesu - <user> -c "/usr/bin/ksh -s a": No such file or directory

---------- Post updated at 14:57 ---------- Previous update was at 14:29 ----------

sorted - when passed as a variable the apostrophes are implicit. Finally got it working - thanks for those who input:

Code:

command='/usr/seos/bin/sesu - <user> -c "/usr/bin/ksh -s a"'

ssh <user>@<server> $command

Works very nicely and you can include a here document then as so:

Code:

command='/usr/seos/bin/sesu - <user> -c "/usr/bin/ksh -s a"'

ssh <user>@<server> $command << "EOF"
echo $1
date
EOF

This will then echo "a" out and you can have a nice long list of commands from the here doc to run on the remote box. You can even log it locally as so:

Code:

command='/usr/seos/bin/sesu - <user> -c "/usr/bin/ksh -s a"'

ssh <user>@<server> $command << "EOF" >> <logfile>
echo $1
date
EOF

---------- Post updated at 14:58 ---------- Previous update was at 14:57 ----------

NB QQ I've heard - why setup command as a var?
A: Because then you can generate it as a dynamic statement within a script - very handy!