Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

When using SSH to connect rsync to a remote server, how do you escape spaces and such in the remote path? A simple backslash escapes the space for the local bash prompt, but on the remote machine the space is then being read as a break in the path, thus marking the end of that path.

So when I do rsync -avz /path/to/source/some\ dir/ user@host.tld:/path/to/dest/some\ dir/ what happens is that the remote server is reading that as just /path/to/dest/some/ and since it can't find that destination remotely, because the actual destination is "some dir" rather than just "some".

If I try the same command and escape the backslash and the space to get past the local bash prompt and maintain the backslash for the remote server (three backslashes total: /path/to/dest/some\\\ dir/), it does indeed send the backslash to the remote server, but the remote server then interprets the path as /path/to/dest/some\/ rather than /path/to/dest/some\ dir/ still stripping the space and the characters after it.

If I try to wrap the path with quotes, it behaves pretty much the same way, effectively cutting the path off at the space. So it too only works to get past the local bash prompt.

Initially I was using a path that had a " - " (space-hyphen-space) segment in it, and the remote server was returning an error rsync: on remote machine: -: unknown option which is what started this whole space-escaping endeavor in the first place.

So what must I do to get this working properly with the remote server, without having to remove the spaces or other erroneous characters like hyphens from the remote path?

share|improve this question
    
Try both single & double quotes. –  jftuga Feb 13 '11 at 2:31
    
Javier mentioned this too, and it did end up working, so I've pasted my working code segment in a reply to his answer. –  purefusion Feb 13 '11 at 4:30

3 Answers 3

up vote 4 down vote accepted

on the initiator machine, rsync builds up a command line that invokes the rsync target on the remote machine, then sends that command line using ssh.... as a single string. That single string is passed to the shell to parse, split into arguments and execute rsync. I have no idea why is that done, instead of packing the (already splitted, expanded and unquoted) arguments in some binary-safe container to the remote rsync.

that means that your arguments will be parsed by two different shells, quote and requote accordingly. Usually, i wrap each argument with double-quotes, and then the whole expression on single-quotes. sometimes it's not enough, or it can be complicated if you want the same expression to be used locally and remotely.

in that cases, i usually set some soft links with simple, no-spaces, all-ASCII names, and use that.

share|improve this answer
2  
And the winner is... single+double quotes! Maybe this is different on every server, so if the other answers don't work for some people, perhaps this one will. Here's the successful code I used on the remote side of the rsync command: 'user@host.tld:"/path/to/dest/some\ dir/"' –  purefusion Feb 13 '11 at 4:15
    
Now begs the question, why does THIS work (on my server), but not either of the other options (just wrapping the path in double quotes, or using triple-backslashes)? I'm running CentOS 5 if that matters. –  purefusion Feb 13 '11 at 4:16
    
That shouldn't be necessary. How are you running it? Are you running it using eval or via a call to a function perhaps? –  Mikel Feb 13 '11 at 5:22
    
You are not using single plus double quotes. You are using single quotes plus double quotes plus backslash escapes. THREE levels of quoting. This should be unnecessary. I ask again: How are you running it? –  Mikel Feb 13 '11 at 5:24
    
@Javier "I have no idea why is that done". Presumably so that tilde expansion works. –  Mikel Feb 13 '11 at 5:27

You were on the right track when you said:

If I try the same command and escape the backslash and the space to get past the local bash prompt and maintain the backslash for the remote server

Here's a way I find easiest to do it:

rsync -av dir\ with\ spaces/ server.tld:"dir\ with\ spaces"

and this way works as well.

rsync -av dir\ with\ spaces/ server.tld:dir\\\ with\\\ spaces

Can you post the exact output and any errors you're seeing?

Can you replace rsync on both sides with a wrapper script?

$ sudo su -
# cd /usr/bin
# mv rsync rsync.real
# cat <<'EOF' >rsync
#!/bin/bash
logfile=/home/yourname/rsync.log
date >> "$logfile"
i=1
for arg in "$@"; do
    echo "arg $i: $arg" >> "$logfile"
    i=$((i+1))
done

rsync.real "$@"
EOF
# chmod +x rsync

Then run your rsync again, and it should prove that this way of escaping works, e.g.

Client side:

Sun Feb 13 13:48:12 EST 2011
1: -av
2: dir with spaces/
3: server:dir\ with\ spaces

Server side:

Sun Feb 13 13:48:13 EST 2011
1: --server
2: -vlogDtpre.iL
3: .
4: dir with spaces

In the above example, the fact that the 4th argument on the server (dir with spaces) is all on one line says that the quoting is working correctly.

If this doesn't help, try re-running rsync -v, or rsync -vv, or rsync -vvv. It will give you extra debugging information.

Two other silly suggestions:

  • is the other server a Linux server, and what is your default shell there?
    • maybe it is expanding file names differently than you expect
  • did you forget to add the -a or -r option?
    • I can't tell without seeing your output
share|improve this answer
    
As mentioned in the question's details, I did indeed try both of your first two methods. Perhaps they just don't work on my server. I also didn't feel like messing around with wrapper scripts. I try to stay away from hacking the /usr/bin/... In any case, another more specific way of quoting did indeed work for me, so perhaps it's just my server that's acting this way. Your suggestions may still certainly be viable for people on other servers, or those not running CentOS, if the OS is part of the problem after all. –  purefusion Feb 13 '11 at 4:21
    
So how did you quote it to make it work? –  Mikel Feb 13 '11 at 5:20
    
You are leaving out some vital detail. Please post the actual command you are running, in full. –  Mikel Feb 13 '11 at 5:25

You can just enclose your path in quotes.

share|improve this answer
    
As you may have seen in the question's details, I have indeed already tried this. However, another answer suggested specific quote usage, and that did indeed end up working. :) –  purefusion Feb 13 '11 at 4:17

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.