X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/955c3145c3c7b013eb80ec02352d130575479383..541b23d144e655036b6c3f2cbb7c4aec2f4c599e:/rsync.yo diff --git a/rsync.yo b/rsync.yo index aec04eef..e7fd8faa 100644 --- a/rsync.yo +++ b/rsync.yo @@ -853,9 +853,18 @@ running rsync daemon on the remote host. See the section "USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION" above. Command-line arguments are permitted in COMMAND provided that COMMAND is -presented to rsync as a single argument. For example: +presented to rsync as a single argument. You must use spaces (not tabs +or other whitespace) to separate the command and args from each other, +and you can use single- and/or double-quotes to preserve spaces in an +argument (but not backslashes). Note that doubling a single-quote +inside a single-quoted string gives you a single-quote; likewise for +double-quotes (though you need to pay attention to which quotes your +shell is parsing and which quotes rsync is parsing). Some examples: -quote(tt( -e "ssh -p 2234")) +quote( +tt( -e 'ssh -p 2234')nl() +tt( -e 'ssh -o "ProxyCommand nohup ssh firewall nc -w1 %h %p"')nl() +) (Note that ssh users can alternately customize site-specific connect options in their .ssh/config file.) @@ -1298,11 +1307,9 @@ updated file into a holding directory until the end of the transfer, at which time all the files are renamed into place in rapid succession. This attempts to make the updating of the files a little more atomic. By default the files are placed into a directory named ".~tmp~" in -each file's destination directory, but you can override this by specifying -the bf(--partial-dir) option. (Note that RSYNC_PARTIAL_DIR has no effect -on this value, nor is bf(--partial-dir) considered to be implied for the -purposes of the daemon-config's "refuse options" setting.) -Conflicts with bf(--inplace). +each file's destination directory, but if you've specified the +bf(--partial-dir) option, that directory will be used instead. +Conflicts with bf(--inplace) and bf(--append). This option uses more memory on the receiving side (one bit per file transferred) and also requires enough free disk space on the receiving