X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/44d98d6166ee27290dc4b9fd3c355d4176aa2979..d5609e969d4f83360f3ece4417a62b34530b8a63:/rsync.yo diff --git a/rsync.yo b/rsync.yo index 4f7b1b9f..b2a8ad99 100644 --- a/rsync.yo +++ b/rsync.yo @@ -1,5 +1,5 @@ mailto(rsync-bugs@samba.org) -manpage(rsync)(1)(30 Sep 2004)()() +manpage(rsync)(1)(28 Feb 2005)()() manpagename(rsync)(faster, flexible replacement for rcp) manpagesynopsis() @@ -49,39 +49,32 @@ There are eight different ways of using rsync. They are: itemize( it() for copying local files. This is invoked when neither source nor destination path contains a : separator - it() for copying from the local machine to a remote machine using a remote shell program as the transport (such as ssh or rsh). This is invoked when the destination path contains a single : separator. - it() for copying from a remote machine to the local machine using a remote shell program. This is invoked when the source contains a : separator. - it() for copying from a remote rsync server to the local machine. This is invoked when the source path contains a :: separator or an rsync:// URL. - it() for copying from the local machine to a remote rsync server. This is invoked when the destination path contains a :: separator or an rsync:// URL. - it() for copying from a remote machine using a remote shell program as the transport, using rsync server on the remote machine. This is invoked when the source path contains a :: - separator and the --rsh=COMMAND (aka "-e COMMAND") option is + separator and the bf(--rsh=COMMAND) (aka "bf(-e COMMAND)") option is also provided. - it() for copying from the local machine to a remote machine using a remote shell program as the transport, using rsync server on the remote machine. This is invoked when the destination path contains a :: separator and the - --rsh=COMMAND option is also provided. - + bf(--rsh=COMMAND) option is also provided. it() for listing files on a remote machine. This is done the same way as rsync transfers except that you leave off the - local destination. + local destination. ) Note that in all cases (other than listing) at least one of the source @@ -97,14 +90,14 @@ 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. -You can also specify any remote shell you like, either by using the -e +You can also specify any remote shell you like, either by using the bf(-e) command line option, or by setting the RSYNC_RSH environment variable. One common substitute is to use ssh, which offers a high degree of security. Note that rsync must be installed on both the source and destination -machines. +machines. manpagesection(USAGE) @@ -113,7 +106,7 @@ and a destination, one of which may be remote. Perhaps the best way to explain the syntax is with some examples: -quote(rsync -t *.c foo:src/) +quote(tt(rsync -t *.c foo:src/)) This would transfer all files matching the pattern *.c from the current directory to the directory src on the machine foo. If any of @@ -121,7 +114,7 @@ the files already exist on the remote system then the rsync remote-update protocol is used to update the file by sending only the differences. See the tech report for details. -quote(rsync -avz foo:src/bar /data/tmp) +quote(tt(rsync -avz foo:src/bar /data/tmp)) 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 @@ -130,7 +123,7 @@ 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. -quote(rsync -avz foo:src/bar/ /data/tmp) +quote(tt(rsync -avz foo:src/bar/ /data/tmp)) 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 @@ -141,32 +134,33 @@ destination. In other words, each of the following commands copies the files in the same way, including their setting of the attributes of /dest/foo: -quote(rsync -av /src/foo /dest) -quote(rsync -av /src/foo/ /dest/foo) +quote( +tt(rsync -av /src/foo /dest)nl() +tt(rsync -av /src/foo/ /dest/foo)nl() +) You can also use rsync in local-only mode, where both the source and destination don't have a ':' in the name. In this case it behaves like an improved copy command. -quote(rsync somehost.mydomain.com::) +quote(tt(rsync somehost.mydomain.com::)) This would list all the anonymous rsync modules available on the host somehost.mydomain.com. (See the following section for more details.) - manpagesection(ADVANCED USAGE) The syntax for requesting multiple files from a remote host involves using quoted spaces in the SRC. Some examples: -quote(rsync host::'modname/dir1/file1 modname/dir2/file2' /dest) +quote(tt(rsync host::'modname/dir1/file1 modname/dir2/file2' /dest)) This would copy file1 and file2 into /dest from an rsync daemon. Each additional arg must include the same "modname/" prefix as the first one, and must be preceded by a single space. All other spaces are assumed to be a part of the filenames. -quote(rsync -av host:'dir1/file1 dir2/file2' /dest) +quote(tt(rsync -av host:'dir1/file1 dir2/file2' /dest)) This would copy file1 and file2 into /dest using a remote shell. This word-splitting is done by the remote shell, so if it doesn't work it means @@ -176,18 +170,19 @@ a filename that contains whitespace, you'll need to either escape the whitespace in a way that the remote shell will understand, or use wildcards in place of the spaces. Two examples of this are: -quote(rsync -av host:'file\ name\ with\ spaces' /dest) -quote(rsync -av host:file?name?with?spaces /dest) +quote( +tt(rsync -av host:'file\ name\ with\ spaces' /dest)nl() +tt(rsync -av host:file?name?with?spaces /dest)nl() +) This latter example assumes that your shell passes through unmatched wildcards. If it complains about "no match", put the name in quotes. - manpagesection(CONNECTING TO AN RSYNC SERVER) It is also possible to use rsync without a remote shell as the transport. In this case you will connect to a remote rsync server -running on TCP port 873. +running on TCP port 873. You may establish the connection via a web proxy by setting the environment variable RSYNC_PROXY to a hostname:port pair pointing to @@ -198,15 +193,12 @@ Using rsync in this way is the same as using it with a remote shell except that: itemize( - it() you use a double colon :: instead of a single colon to - separate the hostname from the path or an rsync:// URL. - + it() you either use a double colon :: instead of a single colon to + separate the hostname from the path, or you use an rsync:// URL. it() the remote server may print a message of the day when you connect. - it() if you specify no path name on the remote server then the list of accessible paths on the server will be shown. - it() if you specify no local destination then a listing of the specified files on the remote server is provided. ) @@ -214,11 +206,11 @@ itemize( Some paths on the remote server may require authentication. If so then you will receive a password prompt when you connect. You can avoid the password prompt by setting the environment variable RSYNC_PASSWORD to -the password you want to use or using the --password-file option. This +the password you want to use or using the bf(--password-file) option. This may be useful when scripting rsync. WARNING: On some systems environment variables are visible to all -users. On those systems using --password-file is recommended. +users. On those systems using bf(--password-file) is recommended. manpagesection(CONNECTING TO AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM) @@ -228,35 +220,36 @@ rsh for transport. This is especially useful when you want to connect to a remote machine via ssh (for encryption or to get through a firewall), but you still want to have access to the rsync server features (see RUNNING AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM, -below). +below). From the user's perspective, using rsync in this way is the same as using it to connect to an rsync server, except that you must explicitly set the remote shell program on the command line with ---rsh=COMMAND. (Setting RSYNC_RSH in the environment will not turn on +bf(--rsh=COMMAND). (Setting RSYNC_RSH in the environment will not turn on this functionality.) In order to distinguish between the remote-shell user and the rsync server user, you can use '-l user' on your remote-shell command: -quote(rsync -av --rsh="ssh -l ssh-user" rsync-user@host::module[/path] local-path) +verb( rsync -av --rsh="ssh -l ssh-user" \ + rsync-user@host::module[/path] local-path) The "ssh-user" will be used at the ssh level; the "rsync-user" will be used to check against the rsyncd.conf on the remote host. manpagesection(RUNNING AN RSYNC SERVER) -An rsync server is configured using a configuration file. Please see the +An rsync server is configured using a configuration file. Please see the rsyncd.conf(5) man page for more information. By default the configuration file is called /etc/rsyncd.conf, unless rsync is running over a remote shell program and is not running as root; in that case, the default name -is rsyncd.conf in the current directory on the remote computer +is rsyncd.conf in the current directory on the remote computer (typically $HOME). manpagesection(RUNNING AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM) See the rsyncd.conf(5) man page for full information on the rsync -server configuration file. +server configuration file. Several configuration options will not be available unless the remote user is root (e.g. chroot, setuid/setgid, etc.). There is no need to @@ -273,7 +266,7 @@ Here are some examples of how I use rsync. To backup my wife's home directory, which consists of large MS Word files and mail folders, I use a cron job that runs -quote(rsync -Cavz . arvidsjaur:backup) +quote(tt(rsync -Cavz . arvidsjaur:backup)) each night over a PPP connection to a duplicate directory on my machine "arvidsjaur". @@ -281,34 +274,29 @@ each night over a PPP connection to a duplicate directory on my machine To synchronize my samba source trees I use the following Makefile targets: -quote( get:nl() - rsync -avuzb --exclude '*~' samba:samba/ . - - put:nl() - rsync -Cavuzb . samba:samba/ - - sync: get put) +verb( get: + rsync -avuzb --exclude '*~' samba:samba/ . + put: + rsync -Cavuzb . samba:samba/ + sync: get put) 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't very efficient. +connection. I then do CVS operations on the remote machine, which saves a +lot of time as the remote CVS protocol isn't very efficient. I mirror a directory between my "old" and "new" ftp sites with the -command +command: -quote(rsync -az -e ssh --delete ~ftp/pub/samba/ nimbus:"~ftp/pub/tridge/samba") +tt(rsync -az -e ssh --delete ~ftp/pub/samba nimbus:"~ftp/pub/tridge") -this is launched from cron every few hours. +This is launched from cron every few hours. manpagesection(OPTIONS SUMMARY) Here is a short summary of the options available in rsync. Please refer -to the detailed description below for a complete description. - -verb( +to the detailed description below for a complete description. verb( -v, --verbose increase verbosity -q, --quiet suppress non-error messages - -c, --checksum always checksum -c, --checksum skip based on checksum, not mod-time & size -a, --archive archive mode; same as -rlptgoD (no -H) -r, --recursive recurse into directories @@ -335,14 +323,15 @@ verb( -O, --omit-dir-times omit directories when preserving times -S, --sparse handle sparse files efficiently -n, --dry-run show what would have been transferred - -W, --whole-file copy files whole + -W, --whole-file copy files whole (without rsync algorithm) --no-whole-file always use incremental rsync 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=PATH specify path to rsync on the remote machine + --rsync-path=PROGRAM specify the rsync to run on remote machine --existing only update files that already exist --ignore-existing ignore files that already exist on receiver + --remove-sent-files sent files/symlinks are removed from sender --del an alias for --delete-during --delete delete files that don't exist on sender --delete-before receiver deletes before transfer (default) @@ -361,21 +350,22 @@ verb( -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 - -T --temp-dir=DIR create temporary files in directory DIR + -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 --copy-dest=DIR ... and include copies of unchanged files --link-dest=DIR hardlink to files in DIR when unchanged - -z, --compress compress file data + -z, --compress compress file data during the transfer -C, --cvs-exclude auto-ignore files in the same way CVS does -f, --filter=RULE add a file-filtering RULE - -F same as --filter=': /.rsync-filter' + -F same as --filter='dir-merge /.rsync-filter' repeated: --filter='- .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-from=FILE read include patterns from FILE --files-from=FILE read list of source-file names from FILE - -0 --from0 all *from file lists are delimited by nulls + -0, --from0 all *from file lists are delimited by nulls --version print version number --port=PORT specify double-colon alternate port number --blocking-io use blocking I/O for the remote shell @@ -383,31 +373,30 @@ verb( --stats give some file-transfer stats --progress show progress during transfer -P same as --partial --progress + -i, --itemize-changes output a change-summary for all updates --log-format=FORMAT log file-transfers using specified format --password-file=FILE read password from FILE --list-only list the files instead of copying them --bwlimit=KBPS limit I/O bandwidth; KBytes per second - --write-batch=FILE write a batched update to FILE + --write-batch=FILE write a batched update to FILE --read-batch=FILE read a batched update from FILE --checksum-seed=NUM set block/file checksum seed (advanced) - -4 --ipv4 prefer IPv4 - -6 --ipv6 prefer IPv6 - -h, --help show this help screen -) - -Rsync can also be run as a daemon, in which case the following options are accepted: + -4, --ipv4 prefer IPv4 + -6, --ipv6 prefer IPv6 + -h, --help show this help screen) -verb( +Rsync can also be run as a daemon, in which case the following options are +accepted: verb( --daemon run as an rsync daemon --address=ADDRESS bind to the specified address --bwlimit=KBPS limit I/O bandwidth; KBytes per second --config=FILE specify alternate rsyncd.conf file --no-detach do not detach from the parent --port=PORT listen on alternate port number - -4 --ipv4 prefer IPv4 - -6 --ipv6 prefer IPv6 - -h, --help show this help screen -) + -v, --verbose increase verbosity + -4, --ipv4 prefer IPv4 + -6, --ipv6 prefer IPv6 + -h, --help show this help screen) manpageoptions() @@ -425,12 +414,21 @@ dit(bf(--version)) print the rsync version number and exit. dit(bf(-v, --verbose)) This option increases the amount of information you are given during the transfer. By default, rsync works silently. A -single -v will give you information about what files are being -transferred and a brief summary at the end. Two -v flags will give you +single bf(-v) will give you information about what files are being +transferred and a brief summary at the end. Two bf(-v) flags will give you information on what files are being skipped and slightly more -information at the end. More than two -v flags should only be used if +information at the end. More than two bf(-v) flags should only be used if you are debugging rsync. +Note that the names of the transferred files that are output are done using +a default bf(--log-format) of "%n%L", which tells you just the name of the +file and, if the item is a symlink, where it points. At the single bf(-v) +level of verbosity, this does not mention when a file gets its attributes +changed. If you ask for an itemized list of changed attributes (either +bf(--itemize-changes) or adding "%i" to the bf(--log-format) setting), the +output (on the client) increases to mention all items that are changed in +any way. See the bf(--log-format) option for more details. + dit(bf(-q, --quiet)) This option decreases the amount of information you are given during the transfer, notably suppressing information messages from the remote server. This flag is useful when invoking rsync from @@ -442,17 +440,18 @@ This option turns off this "quick check" behavior. dit(bf(--size-only)) Normally rsync will not transfer any files that are already the same size and have the same modification time-stamp. With the ---size-only option, files will not be transferred if they have the same size, +bf(--size-only) option, files will not be transferred if they have the same size, regardless of timestamp. This is useful when starting to use rsync after using another mirroring system which may not preserve timestamps exactly. -dit(bf(--modify-window)) When comparing two timestamps rsync treats -the timestamps as being equal if they are within the value of -modify_window. This is normally zero, but you may find it useful to -set this to a larger value in some situations. In particular, when -transferring to Windows FAT filesystems which cannot represent times -with a 1 second resolution --modify-window=1 is useful. +dit(bf(--modify-window)) When comparing two timestamps, rsync treats the +timestamps as being equal if they differ by no more than the modify-window +value. This is normally 0 (for an exact match), but you may find it useful +to set this to a larger value in some situations. In particular, when +transferring to or from an MS Windows FAT filesystem (which represents +times with a 2-second resolution), bf(--modify-window=1) is useful +(allowing times to differ by up to 1 second). dit(bf(-c, --checksum)) This forces the sender to checksum all files using a 128-bit MD4 checksum before transfer. The checksum is then @@ -460,16 +459,17 @@ explicitly checked on the receiver and any files of the same name which already exist and have the same checksum and size on the receiver are not transferred. This option can be quite slow. -dit(bf(-a, --archive)) This is equivalent to -rlptgoD. It is a quick +dit(bf(-a, --archive)) This is equivalent to bf(-rlptgoD). It is a quick way of saying you want recursion and want to preserve almost -everything. +everything. The only exception to this is if bf(--files-from) was +specified, in which case bf(-r) is not implied. -Note however that bf(-a) bf(does not preserve hardlinks), because +Note that bf(-a) bf(does not preserve hardlinks), because finding multiply-linked files is expensive. You must separately specify bf(-H). dit(bf(-r, --recursive)) This tells rsync to copy directories -recursively. See also --dirs (-d). +recursively. See also bf(--dirs) (bf(-d)). dit(bf(-R, --relative)) Use relative paths. This means that the full path names specified on the command line are sent to the server rather than @@ -477,61 +477,63 @@ just the last parts of the filenames. This is particularly useful when you want to send several different directories at the same time. For example, if you used the command -verb(rsync /foo/bar/foo.c remote:/tmp/) +quote(tt( rsync /foo/bar/foo.c remote:/tmp/)) then this would create a file called foo.c in /tmp/ on the remote machine. If instead you used -verb(rsync -R /foo/bar/foo.c remote:/tmp/) +quote(tt( rsync -R /foo/bar/foo.c remote:/tmp/)) then a file called /tmp/foo/bar/foo.c would be created on the remote machine -- the full path name is preserved. To limit the amount of path information that is sent, do something like this: -verb(cd /foo -rsync -R bar/foo.c remote:/tmp/) +quote( +tt( cd /foo)nl() +tt( rsync -R bar/foo.c remote:/tmp/)nl() +) That would create /tmp/bar/foo.c on the remote machine. -dit(bf(--no-relative)) Turn off the --relative option. This is only -needed if you want to use --files-from without its implied --relative +dit(bf(--no-relative)) Turn off the bf(--relative) option. This is only +needed if you want to use bf(--files-from) without its implied bf(--relative) file processing. -dit(bf(--no-implied-dirs)) When combined with the --relative option, the +dit(bf(--no-implied-dirs)) When combined with the bf(--relative) option, the implied directories in each path are not explicitly duplicated as part of the transfer. This makes the transfer more optimal and also allows the two sides to have non-matching symlinks in the implied part of the -path. For instance, if you transfer the file "/path/foo/file" with -R, +path. For instance, if you transfer the file "/path/foo/file" with bf(-R), the default is for rsync to ensure that "/path" and "/path/foo" on the destination exactly match the directories/symlinks of the source. Using -the --no-implied-dirs option would omit both of these implied dirs, +the bf(--no-implied-dirs) option would omit both of these implied dirs, which means that if "/path" was a real directory on one machine and a symlink of the other machine, rsync would not try to change this. dit(bf(-b, --backup)) With this option, preexisting destination files are renamed as each file is transferred or deleted. You can control where the backup file goes and what (if any) suffix gets appended using the ---backup-dir and --suffix options. +bf(--backup-dir) and bf(--suffix) options. +Note that if you don't specify bf(--backup-dir), the bf(--omit-dir-times) +option will be enabled. -dit(bf(--backup-dir=DIR)) In combination with the --backup option, this +dit(bf(--backup-dir=DIR)) In combination with the bf(--backup) option, this tells rsync to store all backups in the specified directory. This is very useful for incremental backups. You can additionally -specify a backup suffix using the --suffix option +specify a backup suffix using the bf(--suffix) option (otherwise the files backed up in the specified directory will keep their original filenames). -If DIR is a relative path, it is relative to the destination directory -(which changes in a recursive transfer). dit(bf(--suffix=SUFFIX)) This option allows you to override the default -backup suffix used with the --backup (-b) option. The default suffix is a ~ -if no --backup-dir was specified, otherwise it is an empty string. +backup suffix used with the bf(--backup) (bf(-b)) option. The default suffix is a ~ +if no -bf(-backup-dir) was specified, otherwise it is an empty string. dit(bf(-u, --update)) This forces rsync to skip any files which exist on the destination and have a modified time that is newer than the source file. (If an existing destination file has a modify time equal to the source file's, it will be updated if the sizes are different.) -In the current implementation of --update, a difference of file format +In the current implementation of bf(--update), a difference of file format between the sender and receiver is always considered to be important enough for an update, no matter what date is on the objects. In other words, if the source has a directory or a @@ -544,17 +546,17 @@ and then move it into place. Instead rsync will overwrite the existing file, meaning that the rsync algorithm can't accomplish the full amount of network reduction it might be able to otherwise (since it does not yet try to sort data matches). One exception to this is if you combine the option -with --backup, since rsync is smart enough to use the backup file as the +with bf(--backup), since rsync is smart enough to use the backup file as the basis file for the transfer. This option is useful for transfer of large files with block-based changes or appended data, and also on systems that are disk bound, not network bound. -The option implies --partial (since an interrupted transfer does not delete -the file), but conflicts with --partial-dir and --delay-updates. -Prior to rsync 2.6.4 --inplace was also incompatible with --compare-dest, ---copy-dest, and --link-dest. +The option implies bf(--partial) (since an interrupted transfer does not delete +the file), but conflicts with bf(--partial-dir) and bf(--delay-updates). +Prior to rsync 2.6.4 bf(--inplace) was also incompatible with bf(--compare-dest) +and bf(--link-dest). WARNING: The file's data will be in an inconsistent state during the transfer (and possibly afterward if the transfer gets interrupted), so you @@ -563,10 +565,10 @@ rsync will be unable to update a file in-place that is not writable by the receiving user. dit(bf(-d, --dirs)) Tell the sending side to include any directories that -are encountered. Unlike --recursive, a directory's contents are not copied +are encountered. Unlike bf(--recursive), a directory's contents are not copied unless the directory was specified on the command-line as either "." or a name with a trailing slash (e.g. "foo/"). Without this option or the ---recursive option, rsync will skip all directories it encounters (and +bf(--recursive) option, rsync will skip all directories it encounters (and output a message to that effect for each one). dit(bf(-l, --links)) When symlinks are encountered, recreate the @@ -576,20 +578,20 @@ dit(bf(-L, --copy-links)) When symlinks are encountered, the file that they point to (the referent) is copied, rather than the symlink. In older versions of rsync, this option also had the side-effect of telling the receiving side to follow symlinks, such as symlinks to directories. In a -modern rsync such as this one, you'll need to specify --keep-dirlinks (-K) +modern rsync such as this one, you'll need to specify bf(--keep-dirlinks) (bf(-K)) to get this extra behavior. The only exception is when sending files to -an rsync that is too old to understand -K -- in that case, the -L option -will still have the side-effect of -K on that older receiving rsync. +an rsync that is too old to understand bf(-K) -- in that case, the bf(-L) option +will still have the side-effect of bf(-K) on that older receiving rsync. dit(bf(--copy-unsafe-links)) This tells rsync to copy the referent of symbolic links that point outside the copied tree. Absolute symlinks are also treated like ordinary files, and so are any symlinks in the -source path itself when --relative is used. +source path itself when bf(--relative) is used. dit(bf(--safe-links)) This tells rsync to ignore any symbolic links which point outside the copied tree. All absolute symlinks are -also ignored. Using this option in conjunction with --relative may -give unexpected results. +also ignored. Using this option in conjunction with bf(--relative) may +give unexpected results. dit(bf(-H, --hard-links)) This tells rsync to recreate hard links on the remote system to be the same as the local system. Without this @@ -611,7 +613,7 @@ destination machines is higher than the bandwidth to disk (especially when the "disk" is actually a networked filesystem). This is the default when both the source and destination are specified as local paths. -dit(bf(--no-whole-file)) Turn off --whole-file, for use when it is the +dit(bf(--no-whole-file)) Turn off bf(--whole-file), for use when it is the default. dit(bf(-p, --perms)) This option causes rsync to set the destination @@ -626,14 +628,14 @@ dit(bf(-o, --owner)) This option causes rsync to set the owner of the destination file to be the same as the source file. On most systems, only the super-user can set file ownership. By default, the preservation is done by name, but may fall back to using the ID number in some -circumstances. See the --numeric-ids option for a full discussion. +circumstances. See the bf(--numeric-ids) option for a full discussion. dit(bf(-g, --group)) This option causes rsync to set the group of the destination file to be the same as the source file. If the receiving program is not running as the super-user, only groups that the receiver is a member of will be preserved. By default, the preservation is done by name, but may fall back to using the ID number in some -circumstances. See the --numeric-ids option for a full discussion. +circumstances. See the bf(--numeric-ids) option for a full discussion. dit(bf(-D, --devices)) This option causes rsync to transfer character and block device information to the remote system to recreate these @@ -642,14 +644,15 @@ devices. This option is only available to the super-user. dit(bf(-t, --times)) This tells rsync to transfer modification times along with the files and update them on the remote system. Note that if this option is not used, the optimization that excludes files that have not been -modified cannot be effective; in other words, a missing -t or -a will -cause the next transfer to behave as if it used -I, causing all files to be +modified cannot be effective; in other words, a missing bf(-t) or bf(-a) will +cause the next transfer to behave as if it used bf(-I), causing all files to be updated (though the rsync algorithm will make the update fairly efficient -if the files haven't actually changed, you're much better off using -t). +if the files haven't actually changed, you're much better off using bf(-t)). dit(bf(-O, --omit-dir-times)) This tells rsync to omit directories when -it is preserving modification times (see --times). If NFS is sharing -the directories on the receiving side, it is a good idea to use -O. +it is preserving modification times (see bf(--times)). If NFS is sharing +the directories on the receiving side, it is a good idea to use bf(-O). +This option is inferred if you use bf(--backup) without bf(--backup-dir). dit(bf(-n, --dry-run)) This tells rsync to not do any file transfers, instead it will just report the actions it would have taken. @@ -665,21 +668,17 @@ dit(bf(-x, --one-file-system)) This tells rsync not to cross filesystem boundaries when recursing. This is useful for transferring the contents of only one filesystem. -dit(bf(--existing)) This tells rsync not to create any new files - +dit(bf(--existing)) This tells rsync not to create any new files -- only update files that already exist on the destination. dit(bf(--ignore-existing)) -This tells rsync not to update files that already exist on -the destination. +This tells rsync not to update files that already exist on +the destination. -dit(bf(--max-delete=NUM)) This tells rsync not to delete more than NUM -files or directories. This is useful when mirroring very large trees -to prevent disasters. - -dit(bf(--max-size=SIZE)) This tells rsync to avoid transferring any -file that is larger than the specified SIZE. The SIZE value can be -suffixed with a letter to indicate a size multiplier (K, M, or G) and -may be a fractional value (e.g. "--max-size=1.5m"). +dit(bf(--remove-sent-files)) This tells rsync to remove from the sending +side the files and/or symlinks that are newly created or whose content is +updated on the receiving side. Directories and devices are not removed, +nor are files/symlinks whose attributes are merely changed. dit(bf(--delete)) This tells rsync to delete extraneous files from the receiving side (ones that aren't on the sending side), but only for the @@ -688,62 +687,76 @@ send the whole directory (e.g. "dir" or "dir/") without using a wildcard for the directory's contents (e.g. "dir/*") since the wildcard is expanded by the shell and rsync thus gets a request to transfer individual files, not the files' parent directory. Files that are excluded from transfer are -excluded from being deleted unless you use --delete-excluded. +also excluded from being deleted unless you use the bf(--delete-excluded) +option or mark the rules as only matching on the sending side (see the +include/exclude modifiers in the FILTER RULES section). This option has no effect unless directory recursion is enabled. This option can be dangerous if used incorrectly! It is a very good idea -to run first using the --dry-run option (-n) to see what files would be +to run first using the bf(--dry-run) option (bf(-n)) to see what files would be deleted to make sure important files aren't listed. If the sending side detects any I/O errors, then the deletion of any files at the destination will be automatically disabled. This is to prevent temporary filesystem failures (such as NFS errors) on the sending side causing a massive deletion of files on the -destination. You can override this with the --ignore-errors option. +destination. You can override this with the bf(--ignore-errors) option. -The --delete option may be combined with one of the --delete-WHEN options -without conflict, as well as --delete-excluded. However, if none of the +The bf(--delete) option may be combined with one of the --delete-WHEN options +without conflict, as well as bf(--delete-excluded). However, if none of the --delete-WHEN options are specified, rsync will currently choose the ---delete-before algorithm. A future version may change this to choose the ---delete-during algorithm. See also --delete-after. +bf(--delete-before) algorithm. A future version may change this to choose the +bf(--delete-during) algorithm. See also bf(--delete-after). dit(bf(--delete-before)) Request that the file-deletions on the receiving -side be done before the transfer starts. This is the default if --delete -or --delete-excluded is specified without one of the --delete-WHEN options. -See --delete (which is implied) for more details on file-deletion. +side be done before the transfer starts. This is the default if bf(--delete) +or bf(--delete-excluded) is specified without one of the --delete-WHEN options. +See bf(--delete) (which is implied) for more details on file-deletion. Deleting before the transfer is helpful if the filesystem is tight for space and removing extraneous files would help to make the transfer possible. However, it does introduce a delay before the start of the transfer, -and this delay might cause the transfer to timeout (if --timeout was +and this delay might cause the transfer to timeout (if bf(--timeout) was specified). dit(bf(--delete-during, --del)) Request that the file-deletions on the receiving side be done incrementally as the transfer happens. This is -a faster method than chosing the before- or after-transfer algorithm, +a faster method than choosing the before- or after-transfer algorithm, but it is only supported beginning with rsync version 2.6.4. -See --delete (which is implied) for more details on file-deletion. +See bf(--delete) (which is implied) for more details on file-deletion. dit(bf(--delete-after)) Request that the file-deletions on the receiving side be done after the transfer has completed. This is useful if you are sending new per-directory merge files as a part of the transfer and you want their exclusions to take effect for the delete phase of the current transfer. -See --delete (which is implied) for more details on file-deletion. +See bf(--delete) (which is implied) for more details on file-deletion. dit(bf(--delete-excluded)) In addition to deleting the files on the receiving side that are not on the sending side, this tells rsync to also -delete any files on the receiving side that are excluded (see --exclude). -See --delete (which is implied) for more details on file-deletion. +delete any files on the receiving side that are excluded (see bf(--exclude)). +See the FILTER RULES section for a way to make individual exclusions behave +this way on the receiver, and for a way to protect files from +bf(--delete-excluded). +See bf(--delete) (which is implied) for more details on file-deletion. -dit(bf(--ignore-errors)) Tells --delete to go ahead and delete files +dit(bf(--ignore-errors)) Tells bf(--delete) to go ahead and delete files even when there are I/O errors. dit(bf(--force)) This options tells rsync to delete directories even if they are not empty when they are to be replaced by non-directories. This -is only relevant without --delete because deletions are now done depth-first. -Requires the --recursive option (which is implied by -a) to have any effect. +is only relevant without bf(--delete) because deletions are now done depth-first. +Requires the bf(--recursive) option (which is implied by bf(-a)) to have any effect. + +dit(bf(--max-delete=NUM)) This tells rsync not to delete more than NUM +files or directories (NUM must be non-zero). +This is useful when mirroring very large trees to prevent disasters. + +dit(bf(--max-size=SIZE)) This tells rsync to avoid transferring any +file that is larger than the specified SIZE. The SIZE value can be +suffixed with a letter to indicate a size multiplier (K, M, or G) and +may be a fractional value (e.g. "bf(--max-size=1.5m)"). dit(bf(-B, --block-size=BLOCKSIZE)) This forces the block size used in the rsync algorithm to a fixed value. It is normally selected based on @@ -764,20 +777,28 @@ TO AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM" above. Command-line arguments are permitted in COMMAND provided that COMMAND is presented to rsync as a single argument. For example: -quote(-e "ssh -p 2234") +quote(tt( -e "ssh -p 2234")) (Note that ssh users can alternately customize site-specific connect options in their .ssh/config file.) You can also choose the remote shell program using the RSYNC_RSH -environment variable, which accepts the same range of values as -e. +environment variable, which accepts the same range of values as bf(-e). + +See also the bf(--blocking-io) option which is affected by this option. -See also the --blocking-io option which is affected by this option. +dit(bf(--rsync-path=PROGRAM)) Use this to specify what program is to be run +on the remote machine to start-up rsync. Often used when rsync is not in +the default remote-shell's path (e.g. --rsync-path=/usr/local/bin/rsync). +Note that PROGRAM is run with the help of a shell, so it can be any +program, script, or command sequence you'd care to run, so long as it does +not corrupt the standard-in & standard-out that rsync is using to +communicate. -dit(bf(--rsync-path=PATH)) Use this to specify the path to the copy of -rsync on the remote machine. Useful when it's not in your path. Note -that this is the full path to the binary, not just the directory that -the binary is in. +One tricky example is to set a different default directory on the remote +machine for use with the bf(--relative) option. For instance: + +quote(tt( rsync -avR --rsync-path="cd /a/b && rsync" hst:c/d /e/)) dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a broad range of files that you often don't want to transfer between @@ -786,42 +807,51 @@ a file should be ignored. The exclude list is initialized to: -quote(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state +quote(quote(tt(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state .nse_depinfo *~ #* .#* ,* _$* *$ *.old *.bak *.BAK *.orig *.rej -.del-* *.a *.olb *.o *.obj *.so *.exe *.Z *.elc *.ln core .svn/) +.del-* *.a *.olb *.o *.obj *.so *.exe *.Z *.elc *.ln core .svn/))) then files listed in a $HOME/.cvsignore are added to the list and any files listed in the CVSIGNORE environment variable (all cvsignore names are delimited by whitespace). Finally, any file is ignored if it is in the same directory as a -.cvsignore file and matches one of the patterns listed therein. +.cvsignore file and matches one of the patterns listed therein. Unlike +rsync's filter/exclude files, these patterns are split on whitespace. See the bf(cvs(1)) manual for more information. +If you're combining bf(-C) with your own bf(--filter) rules, you should +note that these CVS excludes are appended at the end of your own rules, +regardless of where the bf(-C) was placed on the command-line. This makes them +a lower priority than any rules you specified explicitly. If you want to +control where these CVS excludes get inserted into your filter rules, you +should omit the bf(-C) as a command-line option and use a combination of +bf(--filter=:C) and bf(--filter=-C) (either on your command-line or by +putting the ":C" and "-C" rules into a filter file with your other rules). +The first option turns on the per-directory scanning for the .cvsignore +file. The second option does a one-time import of the CVS excludes +mentioned above. + dit(bf(-f, --filter=RULE)) This option allows you to add rules to selectively exclude certain files from the list of files to be transferred. This is most useful in combination with a recursive transfer. -You may use as many --filter options on the command line as you like +You may use as many bf(--filter) options on the command line as you like to build up the list of files to exclude. See the FILTER RULES section for detailed information on this option. -dit(bf(-F)) The -F option is a shorthand for adding two --filter rules to +dit(bf(-F)) The bf(-F) option is a shorthand for adding two bf(--filter) rules to your command. The first time it is used is a shorthand for this rule: -verb( - --filter=': /.rsync-filter' -) +quote(tt( --filter=': /.rsync-filter')) This tells rsync to look for per-directory .rsync-filter files that have been sprinkled through the hierarchy and use their rules to filter the -files in the transfer. If -F is repeated, it is a shorthand for this +files in the transfer. If bf(-F) is repeated, it is a shorthand for this rule: -verb( - --filter='- .rsync-filter' -) +quote(tt( --filter='- .rsync-filter')) This filters out the .rsync-filter files themselves from the transfer. @@ -829,19 +859,19 @@ See the FILTER RULES section for detailed information on how these options work. dit(bf(--exclude=PATTERN)) This option is a simplified form of the ---filter option that defaults to an exclude rule and does not allow +bf(--filter) option that defaults to an exclude rule and does not allow the full rule-parsing syntax of normal filter rules. See the FILTER RULES section for detailed information on this option. -dit(bf(--exclude-from=FILE)) This option is similar to the --exclude +dit(bf(--exclude-from=FILE)) This option is similar to the bf(--exclude) option, but instead it adds all exclude patterns listed in the file FILE to the exclude list. Blank lines in FILE and lines starting with ';' or '#' are ignored. If em(FILE) is bf(-) the list will be read from standard input. dit(bf(--include=PATTERN)) This option is a simplified form of the ---filter option that defaults to an include rule and does not allow +bf(--filter) option that defaults to an include rule and does not allow the full rule-parsing syntax of normal filter rules. See the FILTER RULES section for detailed information on this option. @@ -853,45 +883,50 @@ If em(FILE) is "-" the list will be read from standard input. dit(bf(--files-from=FILE)) Using this option allows you to specify the exact list of files to transfer (as read from the specified FILE or "-" for standard input). It also tweaks the default behavior of rsync to make -transferring just the specified files and directories easier. For -instance, the --relative option is enabled by default when this option -is used (use --no-relative if you want to turn that off), all -directories specified in the list are created on the destination (rather -than being noisily skipped without -r), and the -a (--archive) option's -behavior does not imply -r (--recursive) -- specify it explicitly, if -you want it. +transferring just the specified files and directories easier: + +quote(itemize( + it() The bf(--relative) (bf(-R)) option is implied, which preserves the path + information that is specified for each item in the file (use + bf(--no-relative) if you want to turn that off). + it() The bf(--dirs) (bf(-d)) option is implied, which will create directories + specified in the list on the destination rather than noisily skipping + them. + it() The bf(--archive) (bf(-a)) option's behavior does not imply bf(--recursive) + (bf(-r)), so specify it explicitly, if you want it. +)) The file names that are read from the FILE are all relative to the source dir -- any leading slashes are removed and no ".." references are allowed to go higher than the source dir. For example, take this command: -quote(rsync -a --files-from=/tmp/foo /usr remote:/backup) +quote(tt( rsync -a --files-from=/tmp/foo /usr remote:/backup)) If /tmp/foo contains the string "bin" (or even "/bin"), the /usr/bin directory will be created as /backup/bin on the remote host (but the -contents of the /usr/bin dir would not be sent unless you specified -r +contents of the /usr/bin dir would not be sent unless you specified bf(-r) or the names were explicitly listed in /tmp/foo). Also keep in mind -that the effect of the (enabled by default) --relative option is to +that the effect of the (enabled by default) bf(--relative) option is to duplicate only the path info that is read from the file -- it does not force the duplication of the source-spec path (/usr in this case). -In addition, the --files-from file can be read from the remote host +In addition, the bf(--files-from) file can be read from the remote host instead of the local host if you specify a "host:" in front of the file (the host must match one end of the transfer). As a short-cut, you can specify just a prefix of ":" to mean "use the remote end of the transfer". For example: -quote(rsync -a --files-from=:/path/file-list src:/ /tmp/copy) +quote(tt( rsync -a --files-from=:/path/file-list src:/ /tmp/copy)) This would copy all the files specified in the /path/file-list file that was located on the remote "src" host. dit(bf(-0, --from0)) This tells rsync that the filenames it reads from a file are terminated by a null ('\0') character, not a NL, CR, or CR+LF. -This affects --exclude-from, --include-from, --files-from, and any -merged files specified in a --filter rule. -It does not affect --cvs-exclude (since all names read from a .cvsignore +This affects bf(--exclude-from), bf(--include-from), bf(--files-from), and any +merged files specified in a bf(--filter) rule. +It does not affect bf(--cvs-exclude) (since all names read from a .cvsignore file are split on whitespace). dit(bf(-T, --temp-dir=DIR)) This option instructs rsync to use DIR as a @@ -899,6 +934,16 @@ scratch directory when creating temporary copies of the files transferred on the receiving side. The default behavior is to create the temporary files in the receiving directory. +dit(bf(-y, --fuzzy)) This option tells rsync that it should look for a +basis file for any destination file that is missing. The current algorithm +looks in the same directory as the destination file for either a file that +has an identical size and modified-time, or a similarly-named file. If +found, rsync uses the fuzzy basis file to try to speed up the transfer. + +Note that the use of the bf(--delete) option might get rid of any potential +fuzzy-match files, so either use bf(--delete-after) or specify some +filename exclusions if you need to prevent this. + dit(bf(--compare-dest=DIR)) This option instructs rsync to use em(DIR) on the destination machine as an additional hierarchy to compare destination files against doing transfers (if the files are missing in the destination @@ -907,23 +952,31 @@ sender's file, the file will NOT be transferred to the destination directory. This is useful for creating a sparse backup of just files that have changed from an earlier backup. -Beginning in version 2.6.4, multiple --compare-dest directories may be -provided and rsync will search the list in the order specified until it -finds an existing file. That first discovery is used as the basis file, -and also determines if the transfer needs to happen. +Beginning in version 2.6.4, multiple bf(--compare-dest) directories may be +provided, which will cause rsync to search the list in the order specified +for an exact match. +If a match is found that differs only in attributes, a local copy is made +and the attributes updated. +If a match is not found, a basis file from one of the em(DIR)s will be +selected to try to speed up the transfer. If em(DIR) is a relative path, it is relative to the destination directory. -See also --copy-dest and --link-dest. +See also bf(--copy-dest) and bf(--link-dest). dit(bf(--copy-dest=DIR)) This option behaves like bf(--compare-dest), but rsync will also copy unchanged files found in em(DIR) to the destination -directory (using the data in the em(DIR) for an efficient copy). This is -useful for doing transfers to a new destination while leaving existing -files intact, and then doing a flash-cutover when all files have been -successfully transferred. +directory using a local copy. +This is useful for doing transfers to a new destination while leaving +existing files intact, and then doing a flash-cutover when all files have +been successfully transferred. + +Multiple bf(--copy-dest) directories may be provided, which will cause +rsync to search the list in the order specified for an unchanged file. +If a match is not found, a basis file from one of the em(DIR)s will be +selected to try to speed up the transfer. If em(DIR) is a relative path, it is relative to the destination directory. -See also --compare-dest and --link-dest. +See also bf(--compare-dest) and bf(--link-dest). dit(bf(--link-dest=DIR)) This option behaves like bf(--copy-dest), but unchanged files are hard linked from em(DIR) to the destination directory. @@ -931,32 +984,32 @@ The files must be identical in all preserved attributes (e.g. permissions, possibly ownership) in order for the files to be linked together. An example: -verb( - rsync -av --link-dest=$PWD/prior_dir host:src_dir/ new_dir/ -) +quote(tt( rsync -av --link-dest=$PWD/prior_dir host:src_dir/ new_dir/)) -Beginning with version 2.6.4, if more than one --link-dest option is -specified, rsync will try to find an exact match to link with (searching -the list in the order specified), and if not found, a basis file from one -of the em(DIR)s will be selected to try to speed up the transfer. +Beginning in version 2.6.4, multiple bf(--link-dest) directories may be +provided, which will cause rsync to search the list in the order specified +for an exact match. +If a match is found that differs only in attributes, a local copy is made +and the attributes updated. +If a match is not found, a basis file from one of the em(DIR)s will be +selected to try to speed up the transfer. If em(DIR) is a relative path, it is relative to the destination directory. -See also --compare-dest and --copy-dest. +See also bf(--compare-dest) and bf(--copy-dest). Note that rsync versions prior to 2.6.1 had a bug that could prevent ---link-dest from working properly for a non-root user when -o was specified -(or implied by -a). You can work-around this bug by avoiding the -o option +bf(--link-dest) from working properly for a non-root user when bf(-o) was specified +(or implied by bf(-a)). You can work-around this bug by avoiding the bf(-o) option when sending to an old rsync. -dit(bf(-z, --compress)) With this option, rsync compresses any data from -the files that it sends to the destination machine. This -option is useful on slow connections. The compression method used is the -same method that gzip uses. +dit(bf(-z, --compress)) With this option, rsync compresses the file data +as it is sent to the destination machine, which reduces the amount of data +being transmitted -- something that is useful over a slow connection. -Note this this option typically achieves better compression ratios -that can be achieved by using a compressing remote shell, or a -compressing transport, as it takes advantage of the implicit -information sent for matching data blocks. +Note this this option typically achieves better compression ratios that can +be achieved by using a compressing remote shell or a compressing transport +because it takes advantage of the implicit information in the matching data +blocks that are not explicitly sent over the connection. dit(bf(--numeric-ids)) With this option rsync will transfer numeric group and user IDs rather than using user and group names and mapping them @@ -964,7 +1017,7 @@ at both ends. By default rsync will use the username and groupname to determine what ownership to give files. The special uid 0 and the special group -0 are never mapped via user/group names even if the --numeric-ids +0 are never mapped via user/group names even if the bf(--numeric-ids) option is not specified. If a user or group has no name on the source system or it has no match @@ -982,7 +1035,7 @@ dit(bf(--port=PORT)) This specifies an alternate TCP port number to use rather than the default of 873. This is only needed if you are using the double-colon (::) syntax to connect with an rsync daemon (since the URL syntax has a way to specify the port as a part of the URL). See also this -option in the --daemon mode section. +option in the bf(--daemon) mode section. dit(bf(--blocking-io)) This tells rsync to use blocking I/O when launching a remote shell transport. If the remote shell is either rsh or remsh, @@ -990,13 +1043,98 @@ rsync defaults to using blocking I/O, otherwise it defaults to using non-blocking I/O. (Note that ssh prefers non-blocking I/O.) -dit(bf(--no-blocking-io)) Turn off --blocking-io, for use when it is the +dit(bf(--no-blocking-io)) Turn off bf(--blocking-io), for use when it is the default. +dit(bf(-i, --itemize-changes)) Requests a simple itemized list of the +changes that are being made to each file, including attribute changes. +This is exactly the same as specifying bf(--log-format='%i %n%L'). + +The "%i" escape has a cryptic output that is 9 letters long. The general +format is like the string bf(UXcstpoga)), where bf(U) is replaced by the +kind of update being done, bf(X) is replaced by the file-type, and the +other letters represent attributes that may be output if they are being +updated. + +The update types that replace the bf(U) are as follows: + +quote(itemize( + it() A bf(<) means that a file is being transferred to the local host + (received). + it() A bf(>) means that a file is being transferred to the remote host + (sent). + it() A bf(c) means that a local change/creation is occuring for the item + (such as the creation of a directory or a symlink). + it() A bf(h) means that the item is a hard-link to another item (requires + bf(--hard-links)). + it() A bf(.) means that the item only has attributes that are being + changed. + it() A bf(=) means that the item is identical (this only only output for + higher levels of verbosity). +)) + +The file-types that replace the bf(X) are: bf(f) for a file, a bf(d) for a +dir, an bf(L) for a symlink, and a bf(D) for a device. + +The other letters in the string above are the actual letters that +will be output if the associated attribute for the item is being updated or +a "." for no change. Three exceptions to this are: (1) a newly created +item replaces each letter with a "+", (2) an identical item replaces each +letter with a space, and (3) an unknown attribute replaces each letter with +a "?" (this happens when talking to an older rsync). + +The attribute that is associated with each letter is as follows: + +quote(itemize( + it() A bf(c) means the checksum of the file is different and will be + updated by the file transfer (requries bf(--checksum)). + it() A bf(s) means the size of the file is different and will be updated + by the file transfer. + it() A bf(t) means the modification time is different and is being updated + to the server's value (requires bf(--times)). An alternate value of bf(T) + means that the time will be set to the transfer time, which happens + anytime a symlink is transferred, or when a file or device is transferred + without bf(--times). + it() A bf(p) means the permissions are different and are being updated to + the server's value (requires bf(--perms)). + it() An bf(o) means the owner is different and is being updated to the + server's value (requires bf(--owner) and root privileges). + it() A bf(g) means the group is different and is being updated to the + server's value (requires bf(--group) and the authority to set the group). + it() The bf(a) is reserved for a future enhanced version that supports + extended file attributes, such as ACLs. +)) + +One other output is possible: when deleting files, the "%i" will output +the string "deleting" for each item that is being removed (assuming that +you are talking to a recent enough rsync that it logs deletions instead of +outputting them as a verbose message). + dit(bf(--log-format=FORMAT)) This allows you to specify exactly what the -rsync client logs to stdout on a per-file basis. The log format is -specified using the same format conventions as the log format option in -rsyncd.conf. +rsync client outputs to the user on a per-file basis. The format is a text +string containing embedded single-character escape sequences prefixed with +a percent (%) character. For a list of the possible escape characters, see +the "log format" setting in the rsyncd.conf manpage. (Note that this +option does not affect what a daemon logs to its logfile.) + +Specifying this option will mention each file, dir, etc. that gets updated +in a significant way (a transferred file, a recreated symlink/device, or a +touched directory) unless the itemized-changes escape (%i) is included in +the string, in which case the logging of names increases to mention any +item that is updated in any way (as long as the receiving side is version +2.6.4). See the bf(--itemized-changes) option for a description of the +output of "%i". + +The bf(--verbose) option implies a format of "%n%L", but you can use +bf(--log-format) without bv(--verbose) if you like, or you can override +the format of its per-file output using this option. + +Rsync will output the log-format string prior to a file's transfer unless +one of the transfer-statistic escapes is requested, in which case the +logging is done at the end of the file's transfer. When this late logging +is in effect and bf(--progress) is also specified, rsync will also output +the name of the file being transferred prior to its progress information +(followed, of course, by the log-format output). dit(bf(--stats)) This tells rsync to print a verbose set of statistics on the file transfer, allowing you to tell how effective the rsync @@ -1005,80 +1143,89 @@ algorithm is for your data. dit(bf(--partial)) By default, rsync will delete any partially transferred file if the transfer is interrupted. In some circumstances it is more desirable to keep partially transferred files. Using the ---partial option tells rsync to keep the partial file which should +bf(--partial) option tells rsync to keep the partial file which should make a subsequent transfer of the rest of the file much faster. -dit(bf(--partial-dir=DIR)) Turns on --partial mode, but tells rsync to -put a partially transferred file into em(DIR) instead of writing out the -file to the destination dir. Rsync will also use a file found in this -dir as data to speed up the transfer (i.e. when you redo the send after -rsync creates a partial file) and delete such a file after it has served -its purpose. Note that if --whole-file is specified (or implied) that an -existing partial-dir file will not be used to speedup the transfer (since +dit(bf(--partial-dir=DIR)) A better way to keep partial files than the +bf(--partial) option is to specify a em(DIR) that will be used to hold the +partial data (instead of writing it out to the destination file). +On the next transfer, rsync will use a file found in this +dir as data to speed up the resumption of the transfer and then deletes it +after it has served its purpose. +Note that if bf(--whole-file) is specified (or implied), any partial-dir +file that is found for a file that is being updated will simply be removed +(since rsync is sending files without using the incremental rsync algorithm). -Rsync will create the dir if it is missing (just the last dir -- not the -whole path). This makes it easy to use a relative path (such as -"--partial-dir=.rsync-partial") to have rsync create the partial-directory -in the destination file's directory (rsync will also try to remove the em(DIR) -if a partial file was found to exist at the start of the transfer and the -DIR was specified as a relative path). +Rsync will create the em(DIR) if it is missing (just the last dir -- not +the whole path). This makes it easy to use a relative path (such as +"bf(--partial-dir=.rsync-partial)") to have rsync create the +partial-directory in the destination file's directory when needed, and then +remove it again when the partial file is deleted. -If the partial-dir value is not an absolute path, rsync will also add an ---exclude of this value at the end of all your existing excludes. This +If the partial-dir value is not an absolute path, rsync will also add a directory +bf(--exclude) of this value at the end of all your existing excludes. This will prevent partial-dir files from being transferred and also prevent the untimely deletion of partial-dir items on the receiving side. An example: -the above --partial-dir option would add an "--exclude=.rsync-partial/" +the above bf(--partial-dir) option would add an "bf(--exclude=.rsync-partial/)" rule at the end of any other filter rules. Note that if you are supplying your own filter rules, you may need to manually insert a rule for this directory exclusion somewhere higher up in the list so that it has a high enough priority to be effective (e.g., if your rules specify -a trailing --exclude=* rule, the auto-added rule will be ineffective). +a trailing bf(--exclude='*') rule, the auto-added rule would never be +reached). -IMPORTANT: the --partial-dir should not be writable by other users or it +IMPORTANT: the bf(--partial-dir) should not be writable by other users or it is a security risk. E.g. AVOID "/tmp". You can also set the partial-dir value the RSYNC_PARTIAL_DIR environment -variable. Setting this in the environment does not force --partial to be -enabled, but rather it effects where partial files go when --partial is -specified. For instance, instead of using --partial-dir=.rsync-tmp -along with --progress, you could set RSYNC_PARTIAL_DIR=.rsync-tmp in your -environment and then just use the -P option to turn on the use of the -.rsync-tmp dir for partial transfers. The only time that the --partial -option does not look for this environment value is (1) when --inplace was -specified (since --inplace conflicts with --partial-dir), or (2) when ---delay-updates was specified (see below). +variable. Setting this in the environment does not force bf(--partial) to be +enabled, but rather it effects where partial files go when bf(--partial) is +specified. For instance, instead of using bf(--partial-dir=.rsync-tmp) +along with bf(--progress), you could set RSYNC_PARTIAL_DIR=.rsync-tmp in your +environment and then just use the bf(-P) option to turn on the use of the +.rsync-tmp dir for partial transfers. The only time that the bf(--partial) +option does not look for this environment value is (1) when bf(--inplace) was +specified (since bf(--inplace) conflicts with bf(--partial-dir)), or (2) when +bf(--delay-updates) was specified (see below). + +For the purposes of the server-config's "refuse options" setting, +bf(--partial-dir) does em(not) imply bf(--partial). This is so that a +refusal of the bf(--partial) option can be used to disallow the overwriting +of destination files with a partial transfer, while still allowing the +safer idiom provided by bf(--partial-dir). dit(bf(--delay-updates)) This option puts the temporary file from each -updated file into the file's partial-dir (see above) until the end of the +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. If you don't specify the --partial-dir option, this option will -cause it to default to ".~tmp~" (RSYNC_PARTIAL_DIR is not consulted for -this value). Conflicts with --inplace. +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 server-config's "refuse options" setting.) +Conflicts with bf(--inplace). This option uses more memory on the receiving side (one bit per file transferred) and also requires enough free disk space on the receiving side to hold an additional copy of all the updated files. Note also that -you should not use an absolute path to --partial-dir unless there is no +you should not use an absolute path to bf(--partial-dir) unless there is no chance of any of the files in the transfer having the same name (since all the updated files will be put into a single directory if the path is absolute). See also the "atomic-rsync" perl script in the "support" subdir for an -update algorithm that is even more atomic (it uses --link-dest and a +update algorithm that is even more atomic (it uses bf(--link-dest) and a parallel hierarchy of files). dit(bf(--progress)) This option tells rsync to print information showing the progress of the transfer. This gives a bored user something to watch. -Implies --verbose without incrementing verbosity. +Implies bf(--verbose) if it wasn't already specified. When the file is transferring, the data looks like this: -verb( - 782448 63% 110.64kB/s 0:00:04 -) +verb( 782448 63% 110.64kB/s 0:00:04) This tells you the current file size, the percentage of the transfer that is complete, the current calculated file-completion rate (including both @@ -1087,9 +1234,7 @@ remaining in this transfer. After a file is complete, the data looks like this: -verb( - 1238099 100% 146.38kB/s 0:00:08 (5, 57.1% of 396) -) +verb( 1238099 100% 146.38kB/s 0:00:08 (5, 57.1% of 396)) This tells you the final file size, that it's 100% complete, the final transfer rate for the file, the amount of elapsed time it took to transfer @@ -1097,7 +1242,7 @@ the file, and the addition of a total-transfer summary in parentheses. These additional numbers tell you how many files have been updated, and what percent of the total number of files has been scanned. -dit(bf(-P)) The -P option is equivalent to --partial --progress. Its +dit(bf(-P)) The bf(-P) option is equivalent to bf(--partial) bf(--progress). Its purpose is to make it much easier to specify these two options for a long transfer that may be interrupted. @@ -1111,7 +1256,7 @@ single line. dit(bf(--list-only)) This option will cause the source files to be listed instead of transferred. This option is inferred if there is no destination specified, so you don't usually need to use it explicitly. However, it can -come in handy for a power user that wants to avoid the "-r --exclude="/*/*" +come in handy for a power user that wants to avoid the "bf(-r --exclude='/*/*')" options that rsync might use as a compatibility kluge when generating a non-recursive listing. @@ -1124,18 +1269,18 @@ result is an average transfer rate equaling the specified limit. A value of zero specifies no limit. dit(bf(--write-batch=FILE)) Record a file that can later be applied to -another identical destination with --read-batch. See the "BATCH MODE" +another identical destination with bf(--read-batch). See the "BATCH MODE" section for details. dit(bf(--read-batch=FILE)) Apply all of the changes stored in FILE, a -file previously generated by --write-batch. +file previously generated by bf(--write-batch). If em(FILE) is "-" the batch data will be read from standard input. See the "BATCH MODE" section for details. dit(bf(-4, --ipv4) or bf(-6, --ipv6)) Tells rsync to prefer IPv4/IPv6 when creating sockets. This only affects sockets that rsync has direct control over, such as the outgoing socket when directly contacting an -rsync daemon. See also these options in the --daemon mode section. +rsync daemon. See also these options in the bf(--daemon) mode section. dit(bf(--checksum-seed=NUM)) Set the MD4 checksum seed to the integer NUM. This 4 byte checksum seed is included in each block and file @@ -1146,16 +1291,16 @@ applications that want repeatable block and file checksums, or in the case where the user wants a more random checksum seed. Note that setting NUM to 0 causes rsync to use the default of time() for checksum seed. - enddit() +manpagesection(DAEMON OPTIONS) + The options allowed when starting an rsync daemon are as follows: startdit() - dit(bf(--daemon)) This tells rsync that it is to run as a daemon. The -daemon may be accessed using the bf(host::module) or -bf(rsync://host/module/) syntax. +daemon you start running may be accessed using an rsync client using +the bf(host::module) or bf(rsync://host/module/) syntax. If standard input is a socket then rsync will assume that it is being run via inetd, otherwise it will detach from the current terminal and @@ -1165,20 +1310,20 @@ requests accordingly. See the rsyncd.conf(5) man page for more details. dit(bf(--address)) By default rsync will bind to the wildcard address -when run as a daemon with the --daemon option or when connecting to a -rsync server. The --address option allows you to specify a specific IP +when run as a daemon with the bf(--daemon) option or when connecting to a +rsync server. The bf(--address) option allows you to specify a specific IP address (or hostname) to bind to. This makes virtual hosting possible -in conjunction with the --config option. See also the "address" global +in conjunction with the bf(--config) option. See also the "address" global option in the rsyncd.conf manpage. dit(bf(--bwlimit=KBPS)) This option allows you to specify a maximum transfer rate in kilobytes per second for the data the daemon sends. -The client can still specify a smaller --bwlimit value, but their +The client can still specify a smaller bf(--bwlimit) value, but their requested value will be rounded down if they try to exceed it. See the client version of this option (above) for some extra details. dit(bf(--config=FILE)) This specifies an alternate config file than -the default. This is only relevant when --daemon is specified. +the default. This is only relevant when bf(--daemon) is specified. The default is /etc/rsyncd.conf unless the daemon is running over a remote shell program and the remote user is not root; in that case the default is rsyncd.conf in the current directory (typically $HOME). @@ -1196,16 +1341,20 @@ dit(bf(--port=PORT)) This specifies an alternate TCP port number for the daemon to listen on rather than the default of 873. See also the "port" global option in the rsyncd.conf manpage. +dit(bf(-v, --verbose)) This option increases the amount of information the +daemon logs during its startup phase. After the client connects, the +daemon's verbosity level will be controlled by the options that the client +used and the "max verbosity" setting in the module's config section. + dit(bf(-4, --ipv4) or bf(-6, --ipv6)) Tells rsync to prefer IPv4/IPv6 when creating the incoming sockets that the rsync daemon will use to listen for connections. One of these options may be required in older versions of Linux to work around an IPv6 bug in the kernel (if you see an "address already in use" error when nothing else is using the port, -try specifying --ipv6 or --ipv4 when starting the daemon). +try specifying bf(--ipv6) or bf(--ipv4) when starting the daemon). -dit(bf(-h, --help)) When specified after --daemon, print a short help +dit(bf(-h, --help)) When specified after bf(--daemon), print a short help page describing the options available for starting an rsync daemon. - enddit() manpagesection(FILTER RULES) @@ -1225,51 +1374,57 @@ filename is not skipped. Rsync builds an ordered list of filter rules as specified on the command-line. Filter rules have the following syntax: -itemize( - it() x RULE - it() xMODIFIERS RULE - it() ! +quote( +tt(RULE [PATTERN_OR_FILENAME])nl() +tt(RULE,MODIFIERS [PATTERN_OR_FILENAME])nl() ) -The 'x' is a single-letter that specifies the kind of rule to create. It -can have trailing modifiers, and is separated from the RULE by one of the -following characters: a single space, an equal-sign (=), or an underscore -(_). Here are the available rule prefixes: - -verb( - - specifies an exclude pattern. - + specifies an include pattern. - . specifies a merge-file to read for more rules. - : specifies a per-directory merge-file. - ! clears the current include/exclude list +You have your choice of using either short or long RULE names, as described +below. If you use a short-named rule, the ',' separating the RULE from the +MODIFIERS is optional. The PATTERN or FILENAME that follows (when present) +must come after either a single space or an underscore (_). +Here are the available rule prefixes: + +quote( +bf(exclude, -) specifies an exclude pattern. nl() +bf(include, +) specifies an include pattern. nl() +bf(merge, .) specifies a merge-file to read for more rules. nl() +bf(dir-merge, :) specifies a per-directory merge-file. nl() +bf(hide, H) specifies a pattern for hiding files from the transfer. nl() +bf(show, S) files that match the pattern are not hidden. nl() +bf(protect, P) specifies a pattern for protecting files from deletion. nl() +bf(risk, R) files that match the pattern are not protected. nl() +bf(clear, !) clears the current include/exclude list (takes no arg) nl() ) -Note that the --include/--exclude command-line options do not allow the +When rules are being read from a file, empty lines are ignored, as are +comment lines that start with a "#". + +Note that the bf(--include)/bf(--exclude) command-line options do not allow the full range of rule parsing as described above -- they only allow the -specification of include/exclude patterns and the "!" token (not to -mention the comment lines when reading rules from a file). If a pattern +specification of include/exclude patterns plus a "!" token to clear the +list (and the normal comment parsing when rules are read from a file). +If a pattern does not begin with "- " (dash, space) or "+ " (plus, space), then the rule will be interpreted as if "+ " (for an include option) or "- " (for -an exclude option) were prefixed to the string. A --filter option, on -the other hand, must always contain one of the prefixes above. +an exclude option) were prefixed to the string. A bf(--filter) option, on +the other hand, must always contain either a short or long rule name at the +start of the rule. -Note also that the --filter, --include, and --exclude options take one +Note also that the bf(--filter), bf(--include), and bf(--exclude) options take one rule/pattern each. To add multiple ones, you can repeat the options on -the command-line, use the merge-file syntax of the --filter option, or -the --include-from/--exclude-from options. - -When rules are being read from a file, empty lines are ignored, as are -comment lines that start with a "#". +the command-line, use the merge-file syntax of the bf(--filter) option, or +the bf(--include-from)/bf(--exclude-from) options. manpagesection(INCLUDE/EXCLUDE PATTERN RULES) -You can include and exclude files by specifing patterns using the "+" and -"-" filter rules (as introduced in the FILTER RULES section above). These -rules specify a pattern that is matched against the names of the files -that are going to be transferred. These patterns can take several forms: +You can include and exclude files by specifying patterns using the "+", +"-", etc. filter rules (as introduced in the FILTER RULES section above). +The include/exclude rules each specify a pattern that is matched against +the names of the files that are going to be transferred. These patterns +can take several forms: itemize( - it() if the pattern starts with a / then it is anchored to a particular spot in the hierarchy of files, otherwise it is matched against the end of the pathname. This is similar to a leading ^ in @@ -1286,29 +1441,24 @@ itemize( named "sub". See the section on ANCHORING INCLUDE/EXCLUDE PATTERNS for a full discussion of how to specify a pattern that matches at the root of the transfer. - it() if the pattern ends with a / then it will only match a directory, not a file, link, or device. - it() if the pattern contains a wildcard character from the set *?[ then expression matching is applied using the shell filename matching rules. Otherwise a simple string match is used. - it() the double asterisk pattern "**" will match slashes while a single asterisk pattern "*" will stop at slashes. - it() if the pattern contains a / (not counting a trailing /) or a "**" then it is matched against the full pathname, including any leading directories. If the pattern doesn't contain a / or a "**", then it is matched only against the final component of the filename. (Remember that the algorithm is applied recursively so "full filename" - can actually be any portion of a path fomr the starting directory on + can actually be any portion of a path from the starting directory on down.) - ) -Note that, when using the --recursive (-r) option (which is implied by --a), every subcomponent of every path is visited from the top down, so +Note that, when using the bf(--recursive) (bf(-r)) option (which is implied by +bf(-a)), every subcomponent of every path is visited from the top down, so include/exclude patterns get applied recursively to each subcomponent's full name (e.g. to include "/foo/bar/baz" the subcomponents "/foo" and "/foo/bar" must not be excluded). @@ -1319,26 +1469,26 @@ because rsync did not descend through that excluded section of the hierarchy. This is particularly important when using a trailing '*' rule. For instance, this won't work: -verb( - + /some/path/this-file-will-not-be-found - + /file-is-included - - * +quote( +tt(+ /some/path/this-file-will-not-be-found)nl() +tt(+ /file-is-included)nl() +tt(- *)nl() ) This fails because the parent directory "some" is excluded by the '*' rule, so rsync never visits any of the files in the "some" or "some/path" directories. One solution is to ask for all directories in the hierarchy -to be included by using a single rule: "+_*/" (put it somewhere before the -"-_*" rule). Another solution is to add specific include rules for all +to be included by using a single rule: "+ */" (put it somewhere before the +"- *" rule). Another solution is to add specific include rules for all the parent dirs that need to be visited. For instance, this set of rules works fine: -verb( - + /some/ - + /some/path/ - + /some/path/this-file-is-found - + /file-also-included - - * +quote( +tt(+ /some/)nl() +tt(+ /some/path/)nl() +tt(+ /some/path/this-file-is-found)nl() +tt(+ /file-also-included)nl() +tt(- *)nl() ) Here are some examples of exclude/include matching: @@ -1351,7 +1501,7 @@ itemize( levels below a directory called foo in the transfer-root directory it() "- /foo/**/bar" would exclude any file called bar two or more levels below a directory called foo in the transfer-root directory - it() The combination of "+ */", "+ *.c", and "- *" would include all + it() The combination of "+ */", "+ *.c", and "- *" would include all directories and C source files but nothing else. it() The combination of "+ foo/", "+ foo/bar.c", and "- *" would include only the foo directory and foo/bar.c (the foo directory must be @@ -1361,8 +1511,8 @@ itemize( manpagesection(MERGE-FILE FILTER RULES) You can merge whole files into your filter rules by specifying either a -"." or a ":" filter rule (as introduced in the FILTER RULES section -above). +merge (.) or a dir-merge (:) filter rule (as introduced in the FILTER RULES +section above). There are two kinds of merged files -- single-instance ('.') and per-directory (':'). A single-instance merge file is read one time, and @@ -1378,63 +1528,91 @@ below). Some examples: -verb( - . /etc/rsync/default.rules - : .per-dir-filter - :n- .non-inherited-per-dir-excludes +quote( +tt(merge /etc/rsync/default.rules)nl() +tt(. /etc/rsync/default.rules)nl() +tt(dir-merge .per-dir-filter)nl() +tt(dir-merge,n- .non-inherited-per-dir-excludes)nl() +tt(:n- .non-inherited-per-dir-excludes)nl() ) -The following modifiers are accepted after the "." or ":": +The following modifiers are accepted after a merge or dir-merge rule: itemize( - it() A "-" specifies that the file should consist of only exclude - patterns, with no other rule-parsing except for the list-clearing - token ("!"). - - it() A "+" specifies that the file should consist of only include - patterns, with no other rule-parsing except for the list-clearing - token ("!"). - - it() A "C" is a shorthand for the modifiers "sn-", which makes the - parsing compatible with the way CVS parses their exclude files. If no - filename is specified, ".cvsignore" is assumed. - - it() A "e" will exclude the merge-file from the transfer; e.g. - ":e_.rules" is like ":_.rules" and "-_.rules". - - it() An "n" specifies that the rules are not inherited by subdirectories. - - it() An "s" specifies that the rules are split on all whitespace instead + it() A bf(-) specifies that the file should consist of only exclude + patterns, with no other rule-parsing except for in-file comments. + it() A bf(+) specifies that the file should consist of only include + patterns, with no other rule-parsing except for in-file comments. + it() A bf(C) is a way to specify that the file should be read in a + CVS-compatible manner. This turns on 'n', 'w', and '-', but also + allows the list-clearing token (!) to be specified. If no filename is + provided, ".cvsignore" is assumed. + it() A bf(e) will exclude the merge-file name from the transfer; e.g. + "dir-merge,e .rules" is like "dir-merge .rules" and "- .rules". + it() An bf(n) specifies that the rules are not inherited by subdirectories. + it() A bf(w) specifies that the rules are word-split on whitespace instead of the normal line-splitting. This also turns off comments. Note: the space that separates the prefix from the rule is treated specially, so - "- foo + bar" is parsed as two rules (assuming that "-" or "+" was not - specified to turn off the parsing of prefixes). + "- foo + bar" is parsed as two rules (assuming that prefix-parsing wasn't + also disabled). + it() You may also specify any of the modifiers for the "+" or "-" rules + (below) in order to have the rules that are read-in from the file + default to having that modifier set. For instance, "merge,-/ .excl" would + treat the contents of .excl as absolute-path excludes, + while "dir-merge,s .filt" and ":sC" would each make all their + per-directory rules apply only on the server side. +) + +The following modifiers are accepted after a "+" or "-": + +itemize( + it() A "/" specifies that the include/exclude should be treated as an + absolute path, relative to the root of the filesystem. For example, + "-/ /etc/passwd" would exclude the passwd file any time the transfer + was sending files from the "/etc" directory. + it() A "!" specifies that the include/exclude should take effect if + the pattern fails to match. For instance, "-! */" would exclude all + non-directories. + it() A bf(C) is used to indicate that all the global CVS-exclude rules + should be inserted as excludes in place of the "-C". No arg should + follow. + it() An bf(s) is used to indicate that the rule applies to the sending + side. When a rule affects the sending side, it prevents files from + being transferred. The default is for a rule to affect both sides + unless bf(--delete-excluded) was specified, in which case default rules + become sender-side only. See also the hide (H) and show (S) rules, + which are an alternate way to specify server-side includes/excludes. + it() An bf(r) is used to indicate that the rule applies to the receiving + side. When a rule affects the receiving side, it prevents files from + being deleted. See the bf(s) modifier for more info. See also the + protect (P) and risk (R) rules, which are an alternate way to + specify receiver-side includes/excludes. ) Per-directory rules are inherited in all subdirectories of the directory where the merge-file was found unless the 'n' modifier was used. Each subdirectory's rules are prefixed to the inherited per-directory rules from its parents, which gives the newest rules a higher priority than the -inherited rules. The entire set of per-dir rules is grouped together in +inherited rules. The entire set of dir-merge rules are grouped together in the spot where the merge-file was specified, so it is possible to override -per-dir rules via a rule that got specified earlier in the list of global +dir-merge rules via a rule that got specified earlier in the list of global rules. When the list-clearing rule ("!") is read from a per-directory file, it only clears the inherited rules for the current merge file. -Another way to prevent a single per-dir rule from being inherited is to +Another way to prevent a single rule from a dir-merge file from being inherited is to anchor it with a leading slash. Anchored rules in a per-directory merge-file are relative to the merge-file's directory, so a pattern "/foo" -would only match the file "foo" in the directory where the per-dir filter +would only match the file "foo" in the directory where the dir-merge filter file was found. -Here's an example filter file which you'd specify via --filter=". file": +Here's an example filter file which you'd specify via bf(--filter=". file":) -verb( - . /home/user/.global-filter - - *.gz - : .rules - + *.[ch] - - *.o +quote( +tt(merge /home/user/.global-filter)nl() +tt(- *.gz)nl() +tt(dir-merge .rules)nl() +tt(+ *.[ch])nl() +tt(- *.o)nl() ) This will merge the contents of the /home/user/.global-filter file at the @@ -1446,11 +1624,9 @@ of the transfer). If a per-directory merge-file is specified with a path that is a parent directory of the first transfer directory, rsync will scan all the parent dirs from that starting point to the transfer directory for the indicated -per-directory file. For instance, here is a common filter (see -F): +per-directory file. For instance, here is a common filter (see bf(-F)): -verb( - --filter=': /.rsync-filter' -) +quote(tt(--filter=': /.rsync-filter')) That rule tells rsync to scan for the file .rsync-filter in all directories from the root down through the parent directory of the @@ -1460,10 +1636,10 @@ rsync daemon, the root is always the same as the module's "path".) Some examples of this pre-scanning for per-directory files: -verb( - rsync -avF /src/path/ /dest/dir - rsync -av --filter=': ../../.rsync-filter' /src/path/ /dest/dir - rsync -av --fitler=': .rsync-filter' /src/path/ /dest/dir +quote( +tt(rsync -avF /src/path/ /dest/dir)nl() +tt(rsync -av --filter=': ../../.rsync-filter' /src/path/ /dest/dir)nl() +tt(rsync -av --filter=': .rsync-filter' /src/path/ /dest/dir)nl() ) The first two commands above will look for ".rsync-filter" in "/" and @@ -1473,33 +1649,32 @@ and only looks for the ".rsync-filter" files in each directory that is a part of the transfer. If you want to include the contents of a ".cvsignore" in your patterns, -you should use the rule ":C" -- this is a short-hand for the rule -":sn-_.cvsignore", and ensures that the .cvsignore file's contents are -interpreted according to the same parsing rules that CVS uses. You can -use this to affect where the --cvs-exclude (-C) option's inclusion of the -per-directory .cvsignore file gets placed into your rules by putting a +you should use the rule ":C", which creates a dir-merge of the .cvsignore +file, but parsed in a CVS-compatible manner. You can +use this to affect where the bf(--cvs-exclude) (bf(-C)) option's inclusion of the +per-directory .cvsignore file gets placed into your rules by putting the ":C" wherever you like in your filter rules. Without this, rsync would -add the per-dir rule for the .cvignore file at the end of all your other +add the dir-merge rule for the .cvsignore file at the end of all your other rules (giving it a lower priority than your command-line rules). For example: -verb( - cat < out.dat -) - +quote(tt(ssh remotehost /bin/true > out.dat)) + then look at out.dat. If everything is working correctly then out.dat should be a zero length file. If you are getting the above error from rsync then you will probably find that out.dat contains some text or @@ -1777,62 +1943,55 @@ scripts (such as .cshrc or .profile) that contain output statements for non-interactive logins. If you are having trouble debugging filter patterns, then -try specifying the -vv option. At this level of verbosity rsync will +try specifying the bf(-vv) option. At this level of verbosity rsync will show why each individual file is included or excluded. manpagesection(EXIT VALUES) startdit() dit(bf(0)) Success -dit(bf(1)) Syntax or usage error -dit(bf(2)) Protocol incompatibility +dit(bf(1)) Syntax or usage error +dit(bf(2)) Protocol incompatibility dit(bf(3)) Errors selecting input/output files, dirs dit(bf(4)) Requested action not supported: an attempt was made to manipulate 64-bit files on a platform that cannot support them; or an option was specified that is supported by the client and not by the server. dit(bf(5)) Error starting client-server protocol -dit(bf(10)) Error in socket I/O -dit(bf(11)) Error in file I/O -dit(bf(12)) Error in rsync protocol data stream -dit(bf(13)) Errors with program diagnostics -dit(bf(14)) Error in IPC code -dit(bf(20)) Received SIGUSR1 or SIGINT -dit(bf(21)) Some error returned by waitpid() -dit(bf(22)) Error allocating core memory buffers +dit(bf(10)) Error in socket I/O +dit(bf(11)) Error in file I/O +dit(bf(12)) Error in rsync protocol data stream +dit(bf(13)) Errors with program diagnostics +dit(bf(14)) Error in IPC code +dit(bf(20)) Received SIGUSR1 or SIGINT +dit(bf(21)) Some error returned by waitpid() +dit(bf(22)) Error allocating core memory buffers dit(bf(23)) Partial transfer due to error dit(bf(24)) Partial transfer due to vanished source files -dit(bf(30)) Timeout in data send/receive +dit(bf(30)) Timeout in data send/receive enddit() manpagesection(ENVIRONMENT VARIABLES) startdit() - dit(bf(CVSIGNORE)) The CVSIGNORE environment variable supplements any -ignore patterns in .cvsignore files. See the --cvs-exclude option for +ignore patterns in .cvsignore files. See the bf(--cvs-exclude) option for more details. - dit(bf(RSYNC_RSH)) The RSYNC_RSH environment variable allows you to override the default shell used as the transport for rsync. Command line -options are permitted after the command name, just as in the -e option. - +options are permitted after the command name, just as in the bf(-e) option. dit(bf(RSYNC_PROXY)) The RSYNC_PROXY environment variable allows you to redirect your rsync client to use a web proxy when connecting to a rsync daemon. You should set RSYNC_PROXY to a hostname:port pair. - dit(bf(RSYNC_PASSWORD)) Setting RSYNC_PASSWORD to the required password allows you to run authenticated rsync connections to an rsync daemon without user intervention. Note that this does not supply a password to a shell transport such as ssh. - dit(bf(USER) or bf(LOGNAME)) The USER or LOGNAME environment variables are used to determine the default username sent to an rsync server. If neither is set, the username defaults to "nobody". - dit(bf(HOME)) The HOME environment variable is used to find the user's default .cvsignore file. - enddit() manpagefiles() @@ -1843,20 +2002,18 @@ manpageseealso() rsyncd.conf(5) -manpagediagnostics() - manpagebugs() times are transferred as unix time_t values When transferring to FAT filesystems rsync may re-sync unmodified files. -See the comments on the --modify-window option. +See the comments on the bf(--modify-window) option. file permissions, devices, etc. are transferred as native numerical values -see also the comments on the --delete option +see also the comments on the bf(--delete) option Please report bugs! See the website at url(http://rsync.samba.org/)(http://rsync.samba.org/) @@ -1894,4 +2051,4 @@ rsync was originally written by Andrew Tridgell and Paul Mackerras. Many people have later contributed to it. Mailing lists for support and development are available at -url(http://lists.samba.org)(lists.samba.org) +url(http://lists.samba.org)(lists.samba.org)