[SCM] The rsync repository. - branch master updated
Rsync CVS commit messages
rsync-cvs at lists.samba.org
Wed May 13 07:12:21 UTC 2020
The branch, master has been updated
via 3435ae9b A bit more manpage tweaking.
from 7a929577 Change r'%s' to r'\g<1>%s'.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit 3435ae9bd024814db3a643f73152a2cfc1784952
Author: Wayne Davison <wayne at opencoder.net>
Date: Wed May 13 00:11:57 2020 -0700
A bit more manpage tweaking.
-----------------------------------------------------------------------
Summary of changes:
rsync.yo | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
Changeset truncated at 500 lines:
diff --git a/rsync.yo b/rsync.yo
index b1e4ec3d..474e0288 100644
--- a/rsync.yo
+++ b/rsync.yo
@@ -2626,15 +2626,17 @@ lot of names. (You don't need to specify the bf(--progress) option in
order to use bf(--info=progress2).)
Finally, you can get an instant progress report by sending rsync a signal of
-either SIGINFO or SIGVTALRM On BSD systems a SIGINFO is often generated just by
-typing a Ctrl+T (Linux doesn't currently support a SIGINFO signal). When the
-client-side process receives one of those signals, it will output a single
-progress report when the current file being transferred finishes (so it may
-take a little time if a big file is being handled when the signal arrives).
+either SIGINFO or SIGVTALRM. On BSD systems, a SIGINFO is generated by typing a
+Ctrl+T (Linux doesn't currently support a SIGINFO signal). When the client-side
+process receives one of those signals, it sets a flag to output a single
+progress report which is output when the current file transfer finishes (so it
+may take a little time if a big file is being handled when the signal arrives).
A filename is output (if needed) followed by the --info=progress2 format of
-progress info. You can send the SIGVTALRM signal to all of the rsync processes
-but just the client-side process will respond. Be careful not to send that
-signal to an older rsync, though, or it will die.
+progress info. If you don't know which of the 3 rsync processes is the client
+process, it's OK to signal all of them (since the non-client processes ignore
+the signal).
+
+CAUTION: sending SIGVTALRM to an older rsync (pre-3.2.0) will kill it.
dit(bf(--password-file=FILE)) This option allows you to provide a password for
accessing an rsync daemon via a file or via standard input if bf(FILE) is
--
The rsync repository.
More information about the rsync-cvs
mailing list