Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
liblongpath-rsync
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
liblongpath
liblongpath-rsync
Commits
4e5baafe
Commit
4e5baafe
authored
Jan 22, 2006
by
Wayne Davison
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
More improvements to the -x option (some from Matt & some from me).
parent
0e82af2d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
18 deletions
+17
-18
rsync.yo
rsync.yo
+17
-18
No files found.
rsync.yo
View file @
4e5baafe
...
...
@@ -732,24 +732,23 @@ NOTE: Don't use this option when the destination is a Solaris "tmpfs"
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 recursing into a
directory that is the mount-point for another filesystem, including (as of
2.6.7), "bind" mount-points. You can still copy the contents of multiple
file systems if you include a source dir from each file system -- this just
limits rsync's directory-recursion algorithm.
Rsync will copy the directory at each encountered mount-point unless this
option is repeated. Note, however, that the attributes of this mount-point
directory are copied from those currently visible in the filesystem, not
the inaccessible attributes of the underlying directory.
This option does not affect the "collapsing" of symlinks that options such
as bf(--copy-links) perform, irrespective of what filesystem the symlink's
referent may be on.
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 as a mount point, while other referents are treated as though they
existed on the device where the symlink is found.
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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment