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
4d888108
Commit
4d888108
authored
Jan 23, 2004
by
Wayne Davison
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Some spelling corrections and other simple fixes.
parent
f3219222
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
13 deletions
+13
-13
rsync.yo
rsync.yo
+13
-13
No files found.
rsync.yo
View file @
4d888108
...
...
@@ -77,7 +77,7 @@ itemize(
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=COMM
M
AND option is also provided.
--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
...
...
@@ -111,7 +111,7 @@ manpagesection(USAGE)
You use rsync in the same way you use rcp. You must specify a source
and a destination, one of which may be remote.
Perhaps the best way to explain the syntax is some examples:
Perhaps the best way to explain the syntax is
with
some examples:
quote(rsync *.c foo:src/)
...
...
@@ -162,8 +162,8 @@ 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
your web proxy. Note that your web proxy's configuration must
allow
proxy
ing
to port 873.
your web proxy. Note that your web proxy's configuration must
support
proxy
connections
to port 873.
Using rsync in this way is the same as using it with a remote shell except
that:
...
...
@@ -217,7 +217,7 @@ used to check against the rsyncd.conf on the remote host.
manpagesection(RUNNING AN RSYNC SERVER)
An rsync server is configured using a config file. Please see the
An rsync server is configured using a config
uration
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
...
...
@@ -496,7 +496,7 @@ dit(bf(-W, --whole-file)) With this option the incremental rsync algorithm
is not used and the whole file is sent as-is instead. The transfer may be
faster if this option is used when the bandwidth between the source and
target machines is higher than the bandwidth to disk (especially when the
"disk" is actually a networked file
system). This is the default when both
"disk" is actually a networked filesystem). This is the default when both
the source and target are on the local machine.
dit(bf(--no-whole-file)) Turn off --whole-file, for use when it is the
...
...
@@ -519,7 +519,7 @@ remote system cannot get access to the usernames from /etc/passwd.
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 group name, not group
id
receiver is a member of will be preserved (by group name, not group
ID
number).
dit(bf(-D, --devices)) This option causes rsync to transfer character and
...
...
@@ -602,7 +602,7 @@ remote copies of rsync. Typically, rsync is configured to use ssh by
default, but you may prefer to use rsh on a local network.
If this option is used with bf([user@]host::module/path), then the
remote shell em(COMM
M
AND) will be used to run an rsync server on the
remote shell em(COMMAND) will be used to run an rsync server on the
remote host, and all data will be transmitted through that remote
shell connection, rather than through a direct socket connection to a
running rsync server on the remote host. See the section "CONNECTING
...
...
@@ -748,16 +748,16 @@ compressing transport, as it takes advantage of the implicit
information sent for matching data blocks.
dit(bf(--numeric-ids)) With this option rsync will transfer numeric group
and user
id
s rather than using user and group names and mapping them
and user
ID
s rather than using user and group names and mapping them
at both ends.
By default rsync will use the user
name and group
name to determine
By default rsync will use the user
name and group
name 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
option is not specified.
If the source system is a daemon using chroot, or if a user or group
name does not exist on the destination system, then the numeric
id
name does not exist on the destination system, then the numeric
ID
from the source system is used instead.
dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum IO
...
...
@@ -867,7 +867,7 @@ transfer rate in kilobytes per second. This option is most effective when
using rsync with large files (several megabytes and up). Due to the nature
of rsync transfers, blocks of data are sent, then if rsync determines the
transfer was too fast, it will wait before sending the next data block. The
result is an average transfer rate equal
l
ing the specified limit. A value
result is an average transfer rate equaling the specified limit. A value
of zero specifies no limit.
dit(bf(--write-batch=PREFIX)) Generate a set of files that can be
...
...
@@ -1085,7 +1085,7 @@ ensure the rsync module they copy does not include symbolic links to
bf(/etc/passwd) in the public section of the site. Using
bf(--copy-unsafe-links) will cause any links to be copied as the file
they point to on the destination. Using bf(--safe-links) will cause
unsafe links to be om
m
itted altogether.
unsafe links to be omitted altogether.
Symbolic links are considered unsafe if they are absolute symlinks
(start with bf(/)), empty, or if they contain enough bf("..")
...
...
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