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
ec40899b
Commit
ec40899b
authored
Jan 23, 2004
by
Wayne Davison
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improved comments on --owner and --groups, and removed misinformation
on a chroot daemon (it does not imply --numeric-ids).
parent
b5accaba
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
8 deletions
+14
-8
rsync.yo
rsync.yo
+14
-8
No files found.
rsync.yo
View file @
ec40899b
...
@@ -512,15 +512,20 @@ other files (including updated files) retain their existing permissions
...
@@ -512,15 +512,20 @@ other files (including updated files) retain their existing permissions
dit(bf(-o, --owner)) This option causes rsync to set the owner of the
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,
destination file to be the same as the source file. On most systems,
only the super-user can set file ownership. Note that if the remote system
only the super-user can set file ownership. The preservation is done
is a daemon using chroot, the --numeric-ids option is implied because the
primarily by name, but falls back to using the ID number if the ID has
remote system cannot get access to the usernames from /etc/passwd.
no name on the sending side or has no match on the receiving side.
See also the --numeric-ids option and the "use chroot" setting in the
rsyncd.conf manpage.
dit(bf(-g, --group)) This option causes rsync to set the group of the
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
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
program is not running as the super-user, only groups that the
receiver is a member of will be preserved (by group name, not group ID
receiver is a member of will be preserved. The preservation is done
number).
primarily by name, but falls back to using the ID number if the ID has
no name on the sending side or has no match on the receiving side.
See also the --numeric-ids option and the "use chroot" setting in the
rsyncd.conf manpage.
dit(bf(-D, --devices)) This option causes rsync to transfer character and
dit(bf(-D, --devices)) This option causes rsync to transfer character and
block device information to the remote system to recreate these
block device information to the remote system to recreate these
...
@@ -756,9 +761,10 @@ what ownership to give files. The special uid 0 and the special group
...
@@ -756,9 +761,10 @@ 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 --numeric-ids
option is not specified.
option is not specified.
If the source system is a daemon using chroot, or if a user or group
If a user or group has no name on the source system or it has no match
name does not exist on the destination system, then the numeric ID
on the destination system, then the numeric ID
from the source system is used instead.
from the source system is used instead. See also the comments on the
"use chroot" setting in the rsyncd.conf manpage.
dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum I/O
dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum I/O
timeout in seconds. If no data is transferred for the specified time
timeout in seconds. If no data is transferred for the specified time
...
...
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