81

I'm trying to use rync locally (on a windows machine) to a remote server (my osx box) in order to test a remote deploy build script. I've done rsync before just fine between 2 linux servers, but I'm having problems now. Here is the output:

$ rsync -v -e ssh [email protected]:/Library/WebServer/sites/staging/app1/ ./export

skipping directory /Library/WebServer/sites/staging/app1/.

sent 8 bytes  received 13 bytes  3.82 bytes/sec
total size is 0  speedup is 0.00

$ 

or

$ rsync -avz -e ssh [email protected]:/Library/WebServer/sites/staging/app1/ ./export

receiving file list ... done
./

sent 26 bytes  received 68 bytes  17.09 bytes/sec
total size is 0  speedup is 0.00


$ 

remote app1 directory is empty while local export directory has 4 sub directories and then a bunch of files in each of those

2 Answers 2

111
rsync -v -e ssh myu[email protected]:/Library/WebServer/sites/staging/app1/ ./export

You didn't give it any options to put it into recursive mode like -r or -a.

remote app1 directory is empty while local export directory has 4 sub directories and then a bunch of files in each of those

Do you have the options backwards here? The command should be rsync [source] [DESTINATION]. If the app1 directory is empty and you are trying to copy an empty directory then you aren't going to do anything useful.

Perhaps you need something like this instead?

rsync -avz ./export/  [email protected]:/Library/WebServer/sites/staging/app1/ 

Also:

  • You should almost always include a trailing slash on directories with rsync.
  • Almost every version of rsync released in the last 5-10 years defaults to using ssh has the remote transport. You probably don't have to specify the -e ssh.
4
  • 4
    Wow.. that is quite embarrassing. Yes I mixed up source and dest...
    – chrisan
    Feb 24, 2012 at 20:33
  • 2
    +1 for "You should almost always include a trailing slash on directories with rsync." Oct 18, 2014 at 16:28
  • On Mac it seems to use the -r flag, but on linux I always use -R ("capital R") Aug 24, 2016 at 18:36
  • 1
    @Zoredache Why is it almost?
    – Porcupine
    Sep 16, 2019 at 20:06
4

Trying enabling rsync's built in ability to output a log file, by adding the following option to your command.

--log-file=/path/to/log.file

You can also increase the verbosity by adding an extra -v option, e.g. -avvz, according to the man page, 'Two -v options will give you information on what files are being skipped and slightly more information at the end.'

If this information that returns doesn't help identify the problem, please edit your question and add the additional output.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .