[SCM] The rsync repository. - branch master updated
The branch, master has been updated
via 71177363 A few more minor tweaks.
from bf3e49b4 Improve the daemon info a bit.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit 711773631b406f0285859713ac2b33a6729909a3
Author: Wayne Davison
Date: Thu Sep 1 22:07:54 2022 -0700
A few more minor tweaks.
---
Summary of changes:
rsync.1.md | 8
1 file changed, 4 insertions(+), 4 deletions(-)
Changeset truncated at 500 lines:
diff --git a/rsync.1.md b/rsync.1.md
index 4f235f5b..c62e82ea 100644
--- a/rsync.1.md
+++ b/rsync.1.md
@@ -224,7 +224,7 @@ the hostname omitted. For instance, all these work:
> rsync -aiv host::modname/first ::extra-file{1,2} /dest/
Note that a daemon connection only supports accessing one module per copy
-command, so if the first argument in a follow-up path doesn't begin with the
+command, so if the start of a follow-up path doesn't begin with the
modname of the first path, it is assumed to be a path in the module (such as
the extra-file1 & extra-file2 that are grabbed above).
@@ -260,9 +260,9 @@ that:
- Use either double-colon syntax or rsync:// URL syntax instead of the
single-colon (remote shell) syntax.
-- The first word of (at least) the first "path" is actually a module name.
-- Additional remote source args use an abbreviated syntax as discussed in
- [ADVANCED USAGE](#).
+- The first element of the "path" is actually a module name.
+- Additional remote source args can use an abbreviated syntax that omits the
+ hostname and/or the module name, as discussed in [ADVANCED USAGE](#).
- The remote daemon may print a "message of the day" when you connect.
- If you specify only the host (with no module or path) then a list of
accessible modules on the daemon is output.
--
The rsync repository.
___
rsync-cvs mailing list
rsync-cvs@lists.samba.org
https://lists.samba.org/mailman/listinfo/rsync-cvs
[SCM] The rsync repository. - branch master updated
The branch, master has been updated
via bf3e49b4 Improve the daemon info a bit.
from 034d5e87 Tweak a couple links.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit bf3e49b4530c7a57f16bcf9a57cb41cc35f49852
Author: Wayne Davison
Date: Thu Sep 1 21:56:00 2022 -0700
Improve the daemon info a bit.
---
Summary of changes:
rsync.1.md | 31 +++
1 file changed, 19 insertions(+), 12 deletions(-)
Changeset truncated at 500 lines:
diff --git a/rsync.1.md b/rsync.1.md
index 4d0b8eca..4f235f5b 100644
--- a/rsync.1.md
+++ b/rsync.1.md
@@ -221,7 +221,12 @@ the hostname omitted. For instance, all these work:
> rsync -aiv host:file1 :file2 host:file{3,4} /dest/
> rsync -aiv host::modname/file{1,2} host::modname/extra /dest/
-> rsync -aiv host::modname/first ::modname/extra{1,2} /dest/
+> rsync -aiv host::modname/first ::extra-file{1,2} /dest/
+
+Note that a daemon connection only supports accessing one module per copy
+command, so if the first argument in a follow-up path doesn't begin with the
+modname of the first path, it is assumed to be a path in the module (such as
+the extra-file1 & extra-file2 that are grabbed above).
Really old versions of rsync (2.6.9 and before) only allowed specifying one
remote-source arg, so some people have instead relied on the remote-shell
@@ -253,17 +258,19 @@ section below for information on that.)
Using rsync in this way is the same as using it with a remote shell except
that:
-- you either use a double colon :: instead of a single colon to separate the
- hostname from the path, or you use an rsync:// URL.
-- the first word of the "path" is actually a module name.
-- the remote daemon may print a message of the day when you connect.
-- if you specify no path name on the remote daemon then the list of accessible
- paths on the daemon will be shown.
-- if you specify no local destination then a listing of the specified files on
- the remote daemon is provided.
-- you must not specify the [`--rsh`](#opt) (`-e`) option (since that overrides
- the daemon connection to use ssh -- see [USING RSYNC-DAEMON FEATURES VIA A
- REMOTE-SHELL CONNECTION](#) below).
+- Use either double-colon syntax or rsync:// URL syntax instead of the
+ single-colon (remote shell) syntax.
+- The first word of (at least) the first "path" is actually a module name.
+- Additional remote source args use an abbreviated syntax as discussed in
+ [ADVANCED USAGE](#).
+- The remote daemon may print a "message of the day" when you connect.
+- If you specify only the host (with no module or path) then a list of
+ accessible modules on the daemon is output.
+- If you specify a remote source path but no destination, a listing of the
+ matching files on the remote daemon is output.
+- The [`--rsh`](#opt) (`-e`) option must be omitted to avoid changing the
+ connection style from using a socket connection to [USING RSYNC-DAEMON
+ FEATURES VIA A REMOTE-SHELL CONNECTION](#).
An example that copies all the files in a remote module named "src":
--
The rsync repository.
___
rsync-cvs mailing list
rsync-cvs@lists.samba.org
https://lists.samba.org/mailman/listinfo/rsync-cvs
Re: rsync timeout non-effective
there is connection timeout and I/O timeout i'm using the I/O timeout. for "--timeout" manpage is "if no data is transferredthen rsync will exit" no data is being transferred for hours, but it doesn't exit. so, what's the problem here ? --timeout=SECONDS This option allows you to set a maximum I/O timeout in seconds. If no data is transferred for the specified time then rsync will exit. The default is 0, which means no timeout. --contimeout=SECONDS This option allows you to set the amount of time that rsync will wait for its connection to an rsync daemon to succeed. If the timeout is reached, rsync exits with an error. Am 01.09.22 um 17:32 schrieb Kevin Korb via rsync: You are using rsync over ssh. The connection timeout (and port) options don't matter if rsync isn't doing the networking. On 9/1/22 08:49, Roland via rsync wrote: hello, i do some backup via rsync/ssh and pull data from remote machine to local machine. whenever on remote machine there is some network attached subdir getting "stuck" (i.e. read/write is blocking, eg. by suspended zfs pool because of error), rsync backup also hangs forever. i wonder what's the purpose of "--timeout" then. local machine: 3.1.2 remote machine: 3.2.3 command rsync -avi --stats --delete --delete-excluded --inplace --numeric-ids --out-format=%-15i %-15b %-15l %-20M %n%L --timeout=900 --rsync-path=export PATH=/usr/local/bin:$PATH;rsync --exclude-from=/backup/rsync.exclude.all --exclude-from=/zfspool/backup/myhost/rsync.exclude root@myhost:/ /zfspool/backup/myhost/backup what can i do to make this more robust ? rsync should not hang, as it's getting started via script and the hang blocks backup of other hosts. roland -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync timeout non-effective
You are using rsync over ssh. The connection timeout (and port) options don't matter if rsync isn't doing the networking. On 9/1/22 08:49, Roland via rsync wrote: hello, i do some backup via rsync/ssh and pull data from remote machine to local machine. whenever on remote machine there is some network attached subdir getting "stuck" (i.e. read/write is blocking, eg. by suspended zfs pool because of error), rsync backup also hangs forever. i wonder what's the purpose of "--timeout" then. local machine: 3.1.2 remote machine: 3.2.3 command rsync -avi --stats --delete --delete-excluded --inplace --numeric-ids --out-format=%-15i %-15b %-15l %-20M %n%L --timeout=900 --rsync-path=export PATH=/usr/local/bin:$PATH;rsync --exclude-from=/backup/rsync.exclude.all --exclude-from=/zfspool/backup/myhost/rsync.exclude root@myhost:/ /zfspool/backup/myhost/backup what can i do to make this more robust ? rsync should not hang, as it's getting started via script and the hang blocks backup of other hosts. roland -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: https://sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync timeout non-effective
hello, i do some backup via rsync/ssh and pull data from remote machine to local machine. whenever on remote machine there is some network attached subdir getting "stuck" (i.e. read/write is blocking, eg. by suspended zfs pool because of error), rsync backup also hangs forever. i wonder what's the purpose of "--timeout" then. local machine: 3.1.2 remote machine: 3.2.3 command rsync -avi --stats --delete --delete-excluded --inplace --numeric-ids --out-format=%-15i %-15b %-15l %-20M %n%L --timeout=900 --rsync-path=export PATH=/usr/local/bin:$PATH;rsync --exclude-from=/backup/rsync.exclude.all --exclude-from=/zfspool/backup/myhost/rsync.exclude root@myhost:/ /zfspool/backup/myhost/backup what can i do to make this more robust ? rsync should not hang, as it's getting started via script and the hang blocks backup of other hosts. roland -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
