I'm building a small set of scripts for remotely starting, stopping and checking the status of a process. The stop
of these scripts should look for a process and kill it. Therefore I do:
ssh deploy@hera 'kill -9 `ps -ef | grep MapReduceNode | grep -v "grep" | awk -F " " '{print $2}' | head -n 1`'
The problem here is that the awk tokenization step needs single quotes and these clash with the single quote utilized for executing the remote command via ssh. How can these single quotes be escaped?
Another example is to deal with simple or double quotes because for me for example I needed interpretation and variable replacements. If I want to make a function to display a msg to the macOS of my woman I can do followings:
You can't include a single quote in a single-quoted string. However, that doesn't matter because a single argument can have more than one quoted segment (as long as there is no unquoted whitespace or other self-delimiting characters.)
For example:
However, that command line is very clunky. If possible, you should use the
pkill
utility, which would reduce all that tossh deploy@hera 'pkill -SIGKILL MapReduceNode'
.Otherwise you could do all the string manipulation in a single
awk
invocation (untested, but I think it will work):(unlike the original, this will kill all MapReduceNode tasks rather than some arbitrary first one. If you really want to just do in one task, add
; exit
to the awk action.)This is not
ssh
orawk
handling the quotes, it is the shell (and they are necessary to keep the shell from handling other characters specially, like$
). Nesting them is not supported (although other structures, such as$()
may nest even while containing quotes), so you'll need to escape the single quotes separately. Here are a couple of methods:Use
There are two more options I don't see mentioned in any of the other answers. I've left the grep/grep/awk/head pipeline intact for demonstration purposes, even though (as alluded to in rici's answer) it could be reduced to something like
Using double quotes for the whole ssh command:
Notice that I can use single quotes in the command now, but I have to escape other things I don't want expanded yet:
\$()
(which I've used instead of backticks), double quotes\"
, andprint \$2
.A here-doc with quoted delimiter:
The
-T
prevents ssh complaining about not allocating a pseudo-terminal.The here-doc with quoted delimiter is extra nice because its contents don't have to be modified at all with respect to escaping things, and it can contain single quotes.