-p, --perms preserve permissions
-o, --owner preserve owner (root only)
-g, --group preserve group
- -D, --devices preserve devices (root only)
+ --devices preserve device files (root only)
+ --specials preserve special files
+ -D same as --devices --specials
-t, --times preserve times
-O, --omit-dir-times omit directories when preserving times
--chmod=CHMOD change destination permissions
dit(bf(-d, --dirs)) Tell the sending side to include any directories that
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
+unless the directory name specified is "." or ends with a trailing slash
+(e.g. ".", "dir/.", "dir/", etc.). Without this option or the
bf(--recursive) option, rsync will skip all directories it encounters (and
output a message to that effect for each one). If you specify both
-bf(--dirs) and bf(--recursive), the latter takes precedence.
+bf(--dirs) and bf(--recursive), bf(--recursive) takes precedence.
dit(bf(-l, --links)) When symlinks are encountered, recreate the
symlink on the destination.
is done by name, but may fall back to using the ID number in some
circumstances. See the bf(--numeric-ids) option for a full discussion.
-dit(bf(-D, --devices)) This option causes rsync to transfer character and
+dit(bf(--devices)) This option causes rsync to transfer character and
block device information to the remote system to recreate these
devices. This option is only available to the super-user.
+dit(bf(--specials)) This option causes rsync to transfer special files
+such as named sockets and fifos.
+
+dit(bf(-D)) The bf(-D) option is equivalent to bf(--devices) bf(--specials).
+
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
quote(--chmod=Dg+s,ug+w,Fo-w,+X)
+It is also legal to specify multiple bf(--chmod) options.
+
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.
filesystem. It doesn't seem to handle seeks over null regions
correctly and ends up corrupting the files.
-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(-x, --one-file-system)) This tells rsync to avoid crossing a
+filesystem boundary when recursing. This does not limit the user's ability
+to specify items to copy from multiple filesystems, just rsync's recursion
+through the hierarchy of each directory that the user specified, and also
+the analogous recursion on the receiving side during deletion. Also keep
+in mind that rsync treats a "bind" mount to the same device as being on the
+same filesystem.
+
+If this option is repeated, rsync omits all mount-point directories from
+the copy. Otherwise, it includes an empty directory at each mount-point it
+encounters (using the attributes of the mounted directory because those of
+the underlying mount-point directory are inaccessible).
+
+If rsync has been told to collapse symlinks (via bf(--copy-links) or
+bf(--copy-unsafe-links)), a symlink to a directory on another device is
+treated like a mount-point. Symlinks to non-directories are unaffected
+by this option.
dit(bf(--existing, --ignore-non-existing)) This tells rsync to skip
updating files that do not exist yet on the destination. If this option is
Prior to rsync 2.6.7, this option would have no effect unless bf(--recursive)
was in effect. Beginning with 2.6.7, deletions will also occur when bf(--dirs)
-is specified, but only for directories whose contents are being copied.
+(bf(-d)) is in effect, but only for directories whose contents are being copied.
This option can be dangerous if used incorrectly! It is a very good idea
to run first using the bf(--dry-run) option (bf(-n)) to see what files would be
verbose messages).
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
+format is like the string bf(UXcstpog)), 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
modified.
))
The file-types that replace the bf(X) are: bf(f) for a file, a bf(d) for a
-directory, an bf(L) for a symlink, and a bf(D) for a device.
+directory, an bf(L) for a symlink, a bf(D) for a device, and a bf(S) for a
+special file (e.g. named sockets and fifos).
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
sender's value (requires bf(--owner) and root privileges).
it() A bf(g) means the group is different and is being updated to the
sender'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
Matt McCutchen's Web Site / rsync / rsync.git / blobdiff