@@ -1,6 +1,6 @@

 .SH "NAME"

+rsync \(em a fast, versatile, remote (and local) file-copying tool

 .SH "SYNOPSIS"

 .PP 

 copy locally, to/from another host over any remote shell, or to/from a

 remote rsync daemon.  It offers a large number of options that control

 every aspect of its behavior and permit very flexible specification of the

-set of files to be copied.  It is famous for its delta\-transfer algorithm,

+set of files to be copied.  It is famous for its delta-transfer algorithm,

 which reduces the amount of data sent over the network by sending only the

 differences between the source files and the existing files in the

 destination.  Rsync is widely used for backups and mirroring and as an

 improved copy command for everyday use.

 .PP 

-Rsync finds files that need to be transferred using a \(dq\&quick check\(dq\&

+Rsync finds files that need to be transferred using a \(lqquick check\(rq

 algorithm (by default) that looks for files that have changed in size or

-in last\-modified time.  Any changes in the other preserved attributes (as

+in last-modified time.  Any changes in the other preserved attributes (as

 requested by options) are made on the destination file directly when the

-quick check indicates that the file\(cq\&s data does not need to be updated.

+quick check indicates that the file's data does not need to be updated.

 .PP 

 Some of the additional features of rsync are:

 .PP 

 .IP o 

 support for copying links, devices, owners, groups, and permissions

 .IP o 

-exclude and exclude\-from options similar to GNU tar

+exclude and exclude-from options similar to GNU tar

 .IP o 

 a CVS exclude mode for ignoring the same files that CVS would ignore

 .IP o 

 can use any transparent remote shell, including ssh or rsh

 .IP o 

-does not require super\-user privileges

+does not require super-user privileges

 .IP o 

 pipelining of file transfers to minimize latency costs

 .IP o 

 current host (it does not support copying files between two remote hosts).

 .PP 

 There are two different ways for rsync to contact a remote system: using a

-remote\-shell program as the transport (such as ssh or rsh) or contacting an

-rsync daemon directly via TCP.  The remote\-shell transport is used whenever

+remote-shell program as the transport (such as ssh or rsh) or contacting an

+rsync daemon directly via TCP.  The remote-shell transport is used whenever

 the source or destination path contains a single colon (:) separator after

 a host specification.  Contacting an rsync daemon directly happens when the

 source or destination path contains a double colon (::) separator after a

 host specification, OR when an rsync:// URL is specified (see also the

-\(dq\&USING RSYNC\-DAEMON FEATURES VIA A REMOTE\-SHELL CONNECTION\(dq\& section for

+\(lqUSING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION\(rq section for

 an exception to this latter rule).

 .PP 

 As a special case, if a single source arg is specified without a

-destination, the files are listed in an output format similar to \(dq\&ls \-l\(dq\&.

+destination, the files are listed in an output format similar to \(lqls \-l\(rq.

 .PP 

 As expected, if neither the source or destination path specify a remote

 host, the copy occurs locally (see also the \fB\-\-list\-only\fP option).

 .PP 

-Rsync refers to the local side as the \(dq\&client\(dq\& and the remote side as the

-\(dq\&server\(dq\&.  Don\(cq\&t confuse \(dq\&server\(dq\& with an rsync daemon \-\- a daemon is always a

-server, but a server can be either a daemon or a remote\-shell spawned process.

+Rsync refers to the local side as the \(lqclient\(rq and the remote side as the

+\(lqserver\(rq.  Don't confuse \(lqserver\(rq with an rsync daemon \(em a daemon is always a

+server, but a server can be either a daemon or a remote-shell spawned process.

 .PP 

 .SH "SETUP"

 .PP 

 Once installed, you can use rsync to any machine that you can access via

 a remote shell (as well as some that you can access using the rsync

-daemon\-mode protocol).  For remote transfers, a modern rsync uses ssh

+daemon-mode protocol).  For remote transfers, a modern rsync uses ssh

 for its communications, but it may have been configured to use a

 different remote shell by default, such as rsh or remsh.

 .PP 

 This would transfer all files matching the pattern *.c from the

 current directory to the directory src on the machine foo. If any of

 the files already exist on the remote system then the rsync

-remote\-update protocol is used to update the file by sending only the

+remote-update protocol is used to update the file by sending only the

 differences. See the tech report for details.

 .PP 

 .RS 

 .PP 

 This would recursively transfer all files from the directory src/bar on the

 machine foo into the /data/tmp/bar directory on the local machine. The

-files are transferred in \(dq\&archive\(dq\& mode, which ensures that symbolic

+files are transferred in \(lqarchive\(rq mode, which ensures that symbolic

 links, devices, attributes, permissions, ownerships, etc. are preserved

 in the transfer.  Additionally, compression will be used to reduce the

 size of data portions of the transfer.

 .PP 

 A trailing slash on the source changes this behavior to avoid creating an

 additional directory level at the destination.  You can think of a trailing

-/ on a source as meaning \(dq\&copy the contents of this directory\(dq\& as opposed

-to \(dq\&copy the directory by name\(dq\&, but in both cases the attributes of the

+/ on a source as meaning \(lqcopy the contents of this directory\(rq as opposed

+to \(lqcopy the directory by name\(rq, but in both cases the attributes of the

 containing directory are transferred to the containing directory on the

 destination.  In other words, each of the following commands copies the

 files in the same way, including their setting of the attributes of

 .RE

 .PP 

-Note also that host and module references don\(cq\&t require a trailing slash to

+Note also that host and module references don't require a trailing slash to

 copy the contents of the default directory.  For example, both of these

-copy the remote directory\(cq\&s contents into \(dq\&/dest\(dq\&:

+copy the remote directory's contents into \(lq/dest\(rq:

 .PP 

 .RS 

 \f(CWrsync \-av host: /dest\fP

 .RE

 .PP 

-You can also use rsync in local\-only mode, where both the source and

-destination don\(cq\&t have a \(cq\&:\(cq\& in the name. In this case it behaves like

+You can also use rsync in local-only mode, where both the source and

+destination don't have a \(oq:\(cq in the name. In this case it behaves like

 an improved copy command.

 .PP 

 Finally, you can list all the (listable) modules available from a

 .PP 

 The syntax for requesting multiple files from a remote host is done by

-specifying additional remote\-host args in the same style as the first,

+specifying additional remote-host args in the same style as the first,

 or with the hostname omitted.  For instance, all these work:

 .PP 

 .RS 

 examples:

 .PP 

 .RS 

-\f(CWrsync \-av host:'\&dir1/file1 dir2/file2'\& /dest\fP

+\f(CWrsync \-av host:'dir1/file1 dir2/file2' /dest\fP

 .br 

-\f(CWrsync host::'\&modname/dir1/file1 modname/dir2/file2'\& /dest\fP

+\f(CWrsync host::'modname/dir1/file1 modname/dir2/file2' /dest\fP

 .RE

 .PP 

-This word\-splitting still works (by default) in the latest rsync, but is

+This word-splitting still works (by default) in the latest rsync, but is

 not as easy to use as the first method.

 .PP 

 If you need to transfer a filename that contains whitespace, you can either

-specify the \fB\-\-protect\-args\fP (\fB\-s\fP) option, or you\(cq\&ll need to escape

+specify the \fB\-\-protect\-args\fP (\fB\-s\fP) option, or you'll need to escape

 the whitespace in a way that the remote shell will understand.  For

 instance:

 .PP 

 .RS 

-\f(CWrsync \-av host:'\&file\e name\e with\e spaces'\& /dest\fP

+\f(CWrsync \-av host:'file\e name\e with\e spaces' /dest\fP

 .RE

 .PP 

 you either use a double colon :: instead of a single colon to

 separate the hostname from the path, or you use an rsync:// URL.

 .IP o 

-the first word of the \(dq\&path\(dq\& is actually a module name.

+the first word of the \(lqpath\(rq is actually a module name.

 .IP o 

 the remote daemon may print a message of the day when you

 connect.

 you must not specify the \fB\-\-rsh\fP (\fB\-e\fP) option.

 .PP 

-An example that copies all the files in a remote module named \(dq\&src\(dq\&:

+An example that copies all the files in a remote module named \(lqsrc\(rq:

 .PP 

 .nf 

     rsync \-av host::src /dest

 .PP 

 You may establish the connection via a web proxy by setting the

 environment variable RSYNC_PROXY to a hostname:port pair pointing to

-your web proxy.  Note that your web proxy\(cq\&s configuration must support

+your web proxy.  Note that your web proxy's configuration must support

 proxy connections to port 873.

 .PP 

 You may also establish a daemon connection using a program as a proxy by

 setting the environment variable RSYNC_CONNECT_PROG to the commands you

 wish to run in place of making a direct socket connection.  The string may

-contain the escape \(dq\&%H\(dq\& to represent the hostname specified in the rsync

-command (so use \(dq\&%%\(dq\& if you need a single \(dq\&%\(dq\& in your string).  For

+contain the escape \(lq%H\(rq to represent the hostname specified in the rsync

+command (so use \(lq%%\(rq if you need a single \(lq%\(rq in your string).  For

 example:

 .PP 

 .nf 

-  export RSYNC_CONNECT_PROG='\&ssh proxyhost nc %H 873'\&

+  export RSYNC_CONNECT_PROG='ssh proxyhost nc %H 873'

   rsync \-av targethost1::module/src/ /dest/

   rsync \-av rsync:://targethost2/module/src/ /dest/ 

 .fi 

 which forwards all data to port 873 (the rsync daemon) on the targethost

 (%H).

 .PP 

-.SH "USING RSYNC\-DAEMON FEATURES VIA A REMOTE\-SHELL CONNECTION"

+.SH "USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION"

 .PP 

 It is sometimes useful to use various features of an rsync daemon (such as

 named modules) without actually allowing any new socket connections into a

-system (other than what is already required to allow remote\-shell access).

+system (other than what is already required to allow remote-shell access).

 Rsync supports connecting to a host using a remote shell and then spawning

-a single\-use \(dq\&daemon\(dq\& server that expects to read its config file in the

+a single-use \(lqdaemon\(rq server that expects to read its config file in the

 home dir of the remote user.  This can be useful if you want to encrypt a

-daemon\-style transfer\(cq\&s data, but since the daemon is started up fresh by

+daemon-style transfer's data, but since the daemon is started up fresh by

 the remote user, you may not be able to use features such as chroot or

 change the uid used by the daemon.  (For another way to encrypt a daemon

 transfer, consider using ssh to tunnel a local port to a remote machine and

 configure a normal rsync daemon on that remote host to only allow

-connections from \(dq\&localhost\(dq\&.)

+connections from \(lqlocalhost\(rq.)

 .PP 

-From the user\(cq\&s perspective, a daemon transfer via a remote\-shell

-connection uses nearly the same command\-line syntax as a normal

-rsync\-daemon transfer, with the only exception being that you must

-explicitly set the remote shell program on the command\-line with the

+From the user's perspective, a daemon transfer via a remote-shell

+connection uses nearly the same command-line syntax as a normal

+rsync-daemon transfer, with the only exception being that you must

+explicitly set the remote shell program on the command-line with the

 \fB\-\-rsh=COMMAND\fP option.  (Setting the RSYNC_RSH in the environment

 will not turn on this functionality.)  For example:

 .PP 

 .fi 

 .PP 

-If you need to specify a different remote\-shell user, keep in mind that the

-user@ prefix in front of the host is specifying the rsync\-user value (for a

-module that requires user\-based authentication).  This means that you must

-give the \(cq\&\-l user\(cq\& option to ssh when specifying the remote\-shell, as in

+If you need to specify a different remote-shell user, keep in mind that the

+user@ prefix in front of the host is specifying the rsync-user value (for a

+module that requires user-based authentication).  This means that you must

+give the '\-l user' option to ssh when specifying the remote-shell, as in

 this example that uses the short version of the \fB\-\-rsh\fP option:

 .PP 

 .nf 

-    rsync \-av \-e \(dq\&ssh \-l ssh\-user\(dq\& rsync\-user@host::module /dest

+    rsync \-av \-e "ssh \-l ssh-user" rsync-user@host::module /dest

 .fi 

 .PP 

-The \(dq\&ssh\-user\(dq\& will be used at the ssh level; the \(dq\&rsync\-user\(dq\& will be

-used to log\-in to the \(dq\&module\(dq\&.

+The \(lqssh-user\(rq will be used at the ssh level; the \(lqrsync-user\(rq will be

+used to log-in to the \(lqmodule\(rq.

 .PP 

 .SH "STARTING AN RSYNC DAEMON TO ACCEPT CONNECTIONS"

 daemon already running (or it needs to have configured something like inetd

 to spawn an rsync daemon for incoming connections on a particular port).

 For full information on how to start a daemon that will handling incoming

-socket connections, see the \fBrsyncd.conf\fP(5) man page \-\- that is the config

+socket connections, see the \fBrsyncd.conf\fP(5) man page \(em that is the config

 file for the daemon, and it contains the full details for how to run the

-daemon (including stand\-alone and inetd configurations).

+daemon (including stand-alone and inetd configurations).

 .PP 

-If you\(cq\&re using one of the remote\-shell transports for the transfer, there is

+If you're using one of the remote-shell transports for the transfer, there is

 no need to manually start an rsync daemon.

 .PP 

 .SH "EXAMPLES"

 .PP 

 Here are some examples of how I use rsync.

 .PP 

-To backup my wife\(cq\&s home directory, which consists of large MS Word

+To backup my wife's home directory, which consists of large MS Word

 files and mail folders, I use a cron job that runs

 .PP 

 .RS 

 .PP 

 each night over a PPP connection to a duplicate directory on my machine

-\(dq\&arvidsjaur\(dq\&.

+\(lqarvidsjaur\(rq.

 .PP 

 To synchronize my samba source trees I use the following Makefile

 targets:

 .PP 

 .nf 

     get:

-            rsync \-avuzb \-\-exclude '\&*~'\& samba:samba/ .

+            rsync \-avuzb \-\-exclude '*~' samba:samba/ .

     put:

             rsync \-Cavuzb . samba:samba/

     sync: get put

 .PP 

 this allows me to sync with a CVS directory at the other end of the

 connection. I then do CVS operations on the remote machine, which saves a

-lot of time as the remote CVS protocol isn\(cq\&t very efficient.

+lot of time as the remote CVS protocol isn't very efficient.

 .PP 

-I mirror a directory between my \(dq\&old\(dq\& and \(dq\&new\(dq\& ftp sites with the

+I mirror a directory between my \(lqold\(rq and \(lqnew\(rq ftp sites with the

 command:

 .PP 

-\f(CWrsync \-az \-e ssh \-\-delete ~ftp/pub/samba nimbus:\(dq\&~ftp/pub/tridge\(dq\&\fP

+\f(CWrsync \-az \-e ssh \-\-delete ~ftp/pub/samba nimbus:"~ftp/pub/tridge"\fP

 .PP 

 This is launched from cron every few hours.

 .PP 

 .nf 

  \-v, \-\-verbose               increase verbosity

- \-q, \-\-quiet                 suppress non\-error messages

-     \-\-no\-motd               suppress daemon\-mode MOTD (see caveat)

- \-c, \-\-checksum              skip based on checksum, not mod\-time & size

+ \-q, \-\-quiet                 suppress non-error messages

+     \-\-no\-motd               suppress daemon-mode MOTD (see caveat)

+ \-c, \-\-checksum              skip based on checksum, not mod-time & size

  \-a, \-\-archive               archive mode; equals \-rlptgoD (no \-H,\-A,\-X)

      \-\-no\-OPTION             turn off an implied OPTION (e.g. \-\-no\-D)

  \-r, \-\-recursive             recurse into directories

  \-R, \-\-relative              use relative path names

-     \-\-no\-implied\-dirs       don'\&t send implied dirs with \-\-relative

+     \-\-no\-implied\-dirs       don't send implied dirs with \-\-relative

  \-b, \-\-backup                make backups (see \-\-suffix & \-\-backup\-dir)

      \-\-backup\-dir=DIR        make backups into hierarchy based in DIR

      \-\-suffix=SUFFIX         backup suffix (default ~ w/o \-\-backup\-dir)

  \-u, \-\-update                skip files that are newer on the receiver

-     \-\-inplace               update destination files in\-place

+     \-\-inplace               update destination files in-place

      \-\-append                append data onto shorter files

      \-\-append\-verify         \-\-append w/old data in file checksum

  \-d, \-\-dirs                  transfer directories without recursing

  \-l, \-\-links                 copy symlinks as symlinks

  \-L, \-\-copy\-links            transform symlink into referent file/dir

-     \-\-copy\-unsafe\-links     only \(dq\&unsafe\(dq\& symlinks are transformed

+     \-\-copy\-unsafe\-links     only "unsafe" symlinks are transformed

      \-\-safe\-links            ignore symlinks that point outside the tree

  \-k, \-\-copy\-dirlinks         transform symlink to dir into referent dir

  \-K, \-\-keep\-dirlinks         treat symlinked dir on receiver as dir

      \-\-chmod=CHMOD           affect file and/or directory permissions

  \-A, \-\-acls                  preserve ACLs (implies \-p)

  \-X, \-\-xattrs                preserve extended attributes

- \-o, \-\-owner                 preserve owner (super\-user only)

+ \-o, \-\-owner                 preserve owner (super-user only)

  \-g, \-\-group                 preserve group

-     \-\-devices               preserve device files (super\-user only)

+     \-\-devices               preserve device files (super-user only)

      \-\-specials              preserve special files

  \-D                          same as \-\-devices \-\-specials

  \-t, \-\-times                 preserve modification times

  \-O, \-\-omit\-dir\-times        omit directories from \-\-times

-     \-\-super                 receiver attempts super\-user activities

+     \-\-super                 receiver attempts super-user activities

      \-\-fake\-super            store/recover privileged attrs using xattrs

  \-S, \-\-sparse                handle sparse files efficiently

  \-n, \-\-dry\-run               perform a trial run with no changes made

- \-W, \-\-whole\-file            copy files whole (w/o delta\-xfer algorithm)

- \-x, \-\-one\-file\-system       don'\&t cross filesystem boundaries

- \-B, \-\-block\-size=SIZE       force a fixed checksum block\-size

+ \-W, \-\-whole\-file            copy files whole (w/o delta-xfer algorithm)

+ \-x, \-\-one\-file\-system       don't cross filesystem boundaries

+ \-B, \-\-block\-size=SIZE       force a fixed checksum block-size

  \-e, \-\-rsh=COMMAND           specify the remote shell to use

      \-\-rsync\-path=PROGRAM    specify the rsync to run on remote machine

      \-\-existing              skip creating new files on receiver

      \-\-ignore\-existing       skip updating files that exist on receiver

-     \-\-remove\-source\-files   sender removes synchronized files (non\-dir)

+     \-\-remove\-source\-files   sender removes synchronized files (non-dir)

      \-\-del                   an alias for \-\-delete\-during

      \-\-delete                delete extraneous files from dest dirs

      \-\-delete\-excluded       also delete excluded files from dest dirs

      \-\-ignore\-errors         delete even if there are I/O errors

      \-\-force                 force deletion of dirs even if not empty

-     \-\-max\-delete=NUM        don'\&t delete more than NUM files

-     \-\-max\-size=SIZE         don'\&t transfer any file larger than SIZE

-     \-\-min\-size=SIZE         don'\&t transfer any file smaller than SIZE

+     \-\-max\-delete=NUM        don't delete more than NUM files

+     \-\-max\-size=SIZE         don't transfer any file larger than SIZE

+     \-\-min\-size=SIZE         don't transfer any file smaller than SIZE

      \-\-partial               keep partially transferred files

      \-\-partial\-dir=DIR       put a partially transferred file into DIR

      \-\-delay\-updates         put all updated files into place at end

- \-m, \-\-prune\-empty\-dirs      prune empty directory chains from file\-list

-     \-\-numeric\-ids           don'\&t map uid/gid values by user/group name

+ \-m, \-\-prune\-empty\-dirs      prune empty directory chains from file-list

+     \-\-numeric\-ids           don't map uid/gid values by user/group name

      \-\-timeout=SECONDS       set I/O timeout in seconds

      \-\-contimeout=SECONDS    set daemon connection timeout in seconds

- \-I, \-\-ignore\-times          don'\&t skip files that match size and time

+ \-I, \-\-ignore\-times          don't skip files that match size and time

      \-\-size\-only             skip files that match in size

-     \-\-modify\-window=NUM     compare mod\-times with reduced accuracy

+     \-\-modify\-window=NUM     compare mod-times with reduced accuracy

  \-T, \-\-temp\-dir=DIR          create temporary files in directory DIR

  \-y, \-\-fuzzy                 find similar file for basis if no dest file

      \-\-compare\-dest=DIR      also compare received files relative to DIR

  \-z, \-\-compress              compress file data during the transfer

      \-\-compress\-level=NUM    explicitly set compression level

      \-\-skip\-compress=LIST    skip compressing files with suffix in LIST

- \-C, \-\-cvs\-exclude           auto\-ignore files in the same way CVS does

- \-f, \-\-filter=RULE           add a file\-filtering RULE

- \-F                          same as \-\-filter='\&dir\-merge /.rsync\-filter'\&

-                             repeated: \-\-filter='\&\- .rsync\-filter'\&

+ \-C, \-\-cvs\-exclude           auto-ignore files in the same way CVS does

+ \-f, \-\-filter=RULE           add a file-filtering RULE

+ \-F                          same as \-\-filter='dir-merge /.rsync\-filter'

      \-\-exclude=PATTERN       exclude files matching PATTERN

      \-\-exclude\-from=FILE     read exclude patterns from FILE

-     \-\-include=PATTERN       don'\&t exclude files matching PATTERN

+     \-\-include=PATTERN       don't exclude files matching PATTERN

      \-\-include\-from=FILE     read include patterns from FILE

-     \-\-files\-from=FILE       read list of source\-file names from FILE

+     \-\-files\-from=FILE       read list of source-file names from FILE

  \-0, \-\-from0                 all *from/filter files are delimited by 0s

- \-s, \-\-protect\-args          no space\-splitting; wildcard chars only

+ \-s, \-\-protect\-args          no space-splitting; wildcard chars only

      \-\-address=ADDRESS       bind address for outgoing socket to daemon

-     \-\-port=PORT             specify double\-colon alternate port number

+     \-\-port=PORT             specify double-colon alternate port number

      \-\-sockopts=OPTIONS      specify custom TCP options

      \-\-blocking\-io           use blocking I/O for the remote shell

-     \-\-stats                 give some file\-transfer stats

- \-8, \-\-8\-bit\-output          leave high\-bit chars unescaped in output

- \-h, \-\-human\-readable        output numbers in a human\-readable format

+     \-\-stats                 give some file-transfer stats

+ \-8, \-\-8\-bit\-output          leave high-bit chars unescaped in output

+ \-h, \-\-human\-readable        output numbers in a human-readable format

      \-\-progress              show progress during transfer

  \-P                          same as \-\-partial \-\-progress

- \-i, \-\-itemize\-changes       output a change\-summary for all updates

+ \-i, \-\-itemize\-changes       output a change-summary for all updates

      \-\-out\-format=FORMAT     output updates using the specified FORMAT

-     \-\-log\-file=FILE         log what we'\&re doing to the specified FILE

+     \-\-log\-file=FILE         log what we're doing to the specified FILE

      \-\-log\-file\-format=FMT   log updates using the specified FMT