Some word fixes.

This commit is contained in:
Wayne Davison
2022-03-26 08:28:16 -07:00
parent 13c4019e94
commit 96ed4b47b9
11 changed files with 59 additions and 59 deletions

View File

@@ -177,7 +177,7 @@
- Try to support a client that sent a remote rsync a wacko stderr file handle
(such as an older File::RsyncP perl library used by BackupPC).
- Lots of man page improvements, including better html versions.
- Lots of manpage improvements, including better HTML versions.
### PACKAGING RELATED:

View File

@@ -797,7 +797,7 @@ your home directory (remove the '=' for that).
One side-effect of incremental recursion is that any missing
sub-directories inside a recursively-scanned directory are (by default)
created prior to recursing into the sub-dirs. This earlier creation point
(commpared to a non-incremental recursion) allows rsync to then set the
(compared to a non-incremental recursion) allows rsync to then set the
modify time of the finished directory right away (without having to delay
that until a bunch of recursive copying has finished). However, these
early directories don't yet have their completed mode, mtime, or ownership
@@ -954,9 +954,9 @@ your home directory (remove the '=' for that).
A caution for those that choose to combine [`--inplace`](#opt) with
`--update`: an interrupted transfer will leave behind a partial file on the
receiving side that has a very recent modified time, so re-running the
transfer will probably **not** continue the interrutped file. As such, it
transfer will probably **not** continue the interrupted file. As such, it
is usually best to avoid combining this with[ `--inplace`](#opt) unless you
have implemented manual steps to handle any interrutped in-progress files.
have implemented manual steps to handle any interrupted in-progress files.
0. `--inplace`
@@ -1643,7 +1643,7 @@ your home directory (remove the '=' for that).
0. `--no-whole-file`, `--no-W`
Disable whole-file updating when it is enaled by default for a local
Disable whole-file updating when it is enabled by default for a local
transfer. This usually slows rsync down, but it can be useful if you are
trying to minimize the writes to the destination file (if combined with
[`--inplace`](#opt)) or for testing the checksum-based update algorithm.
@@ -3565,7 +3565,7 @@ your home directory (remove the '=' for that).
socket when directly contacting an rsync daemon, as well as the forwarding
of the `-4` or `-6` option to ssh when rsync can deduce that ssh is being
used as the remote shell. For other remote shells you'll need to specify
the "`--rsh SHELL -4`" option directly (or whatever ipv4/ipv6 hint options
the "`--rsh SHELL -4`" option directly (or whatever IPv4/IPv6 hint options
it uses).
See also [the daemon version of these options](#dopt--ipv4).
@@ -3724,7 +3724,7 @@ is skipped; if it is an include pattern then that filename is not skipped; if
no matching pattern is found, then the filename is not skipped.
Aside: because the interactions of filter rules can be complex, it is useful to
use the `--debug=FILTER` option if things aren't working they way you expect.
use the `--debug=FILTER` option if things aren't working the way you expect.
The level-1 output (the default if no level number is specified) mentions the
filter rule that is first matched by each file in the transfer. It also warns
if a filter rule has trailing whitespace. The level-2 output mentions a lot

View File

@@ -98,9 +98,9 @@ a literal % into a value is to use %%.
0. `motd file`
This parameter allows you to specify a "message of the day" to display to
clients on each connect. This usually contains site information and any
legal notices. The default is no motd file. This can be overridden by the
This parameter allows you to specify a "message of the day" (MOTD) to display
to clients on each connect. This usually contains site information and any
legal notices. The default is no MOTD file. This can be overridden by the
`--dparam=motdfile=FILE` command-line option when starting the daemon.
0. `pid file`
@@ -716,7 +716,7 @@ the values of parameters. See the GLOBAL PARAMETERS section for more details.
addresses which match the masked IP address will be allowed in.
- a hostname pattern using wildcards. If the hostname of the connecting IP
(as determined by a reverse lookup) matches the wildcarded name (using
the same rules as normal unix filename matching), the client is allowed
the same rules as normal Unix filename matching), the client is allowed
in. This only works if "[reverse lookup](#)" is enabled (the default).
- a hostname. A plain hostname is matched against the reverse DNS of the
connecting IP (if "[reverse lookup](#)" is enabled), and/or the IP of the