Matthias Schniedermeyer
2007-Mar-13 17:51 UTC
Feature-Request: --write-batch on destination not source
Hi I have a "Chain" of rsyncs(*) A -> B -> C -> D My problem is that "A" is switched off after the rsync is done. So i have to copy the "batch" immediately (and manually/via other means) to "B", before switching off, so the batch can later be retrieved from "B" and copied to "C" for --read-batch. And copied further on for "D". So for my case if would be great if i could instruct the destination rsync, of the A -> B stage, to write the batch-file. *: Currently the bread and butter: rsync -axH --delete -e ssh Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
Wayne Davison
2007-Mar-13 20:57 UTC
Feature-Request: --write-batch on destination not source
On Tue, Mar 13, 2007 at 06:27:35PM +0100, Matthias Schniedermeyer wrote:> So for my case if would be great if i could instruct the destination > rsync, of the A -> B stage, to write the batch-file.If you ssh into the B system and run the rsync command there, you can write the batch on the destination system that way. If you can't ssh back into A to make the copy, you could check into ssh's port-forwarding options, and use a temporary rsync daemon on A for B to access. I don't plan to make the server able to output the batch file -- I think it's best that the client does that. ..wayne..