I am sorry, the rsync algorithm needs to execute rsync on the server.
Since ftp does not allow executing remote programs (as ssh does), even
if there exists a rsync executable installed in the server and you have
permission to execute it, using ftp you cannot execute it. So your
command won't
Well, for me it seems this is quite unnecessary since it is already
implemented elsewhere: rm -rf upload_dir.
Even the --remove-sent-files seems redundant, since removing files can
always be done with rm, can't it?
Even when using complex rules to select the files, one can parse the
output
I vote for this feature. In du and df commands, this is invoked with:
-h, --human-readable
print sizes in human readable format (e.g., 1K 234M 2G)
--si likewise, but use powers of 1000 not 1024
Currently, in rsync, -h is the short form of --help.
Cheers,
Manuel.
Martin Geisler
Could this also be added to the FAQ ? Please!
Thanks,
Manuel.
Carson Gaspar wrote:
--On Thursday, October 20, 2005 12:53 PM -0700 Wayne Davison
[EMAIL PROTECTED] wrote:
On Wed, Oct 19, 2005 at 10:29:21PM -0400, Matt McCutchen wrote:
$ ssh -L :target:22 -N -f [EMAIL PROTECTED]
Carson Gaspar wrote:
--On Saturday, October 22, 2005 1:56 AM +0100 Manuel López-Ibáñez
[EMAIL PROTECTED] wrote:
This setup seems to work well--perhaps it could be added to the rsync
FAQ page as Method 2b. The only annoyance is that one might still get
two indistinguishable Password:
Oh, yes! I am sorry, I should have checked that twice.
Wayne did really a great work on the FAQ.
I would add something instead (of added to) the Method #. For example,
Method 1: no rsync daemon server, passwordless authentication in middle
machine.
Method 2: no rsync daemon server, using SSH
Yes, your explanations are better. I will promote #2 to become #1, since
it is more likely the one that will work better in all situations.
Another thing is... if you can use Method #2 Rsync SSH-es to target
using a proxy command that first SSH-es to middle also with rsync
daemon servers,
I think you are confusing the 8 different ways of using rsync. You
should read again and more carefully the section GENERAL in manual page
of rsync, rsync(1), for details. Keep reading below:
Adrian Mak wrote:
rsync with ssh, I executed
rsync --verbose --progress --recursive -rsh=/usr/bin/ssh
Actually, rsync is not the transport in this scenario, SSH is. The
Windows system doesn't need to have rsync installed. I'm using rsync
because I want to sync many files within the directory tree (not shown
in my example, which was simplified to just foo.txt to show the error).
-Anthony
Peter van der Meer wrote:
The ProxyCommand option in ssh usually contains space-characters, so it
would not work in your example.
Interpretation by a shell would solve this, but there are other possible
sollutions as well.
True! You are right!
If rsync would give this command to another
The trouble is that rsync parses the -e command into arguments, and it
just splits at every whitespace character without regard for the inner
quotes. Maybe rsync should really be calling on a shell to parse the
command.
Really? Does this mean that any option passed to ssh is interpreted by
This setup seems to work well--perhaps it could be added to the rsync
FAQ page as Method 2b. The only annoyance is that one might still get
two indistinguishable Password: prompts; could someone tell me how to
configure SSH so the prompt reveals the target
Well, actually, I get Password:
Wayne Davison wrote:
On Thu, Oct 20, 2005 at 01:15:54AM +0100, Manuel L?pez-Ib??ez wrote:
For example, isn't it possible for the root of middle (or some
attacker) to get my keys and use them?
No, that's not how ssh keys work at all. Firstly, you only need to put
the *public key* on the
Wayne Davison wrote:
On Thu, Oct 20, 2005 at 06:06:28PM +0100, Manuel L?pez-Ib??ez wrote:
Can rsync work while ssh-agent is forwarding data?
Of course. All rsync needs is an 8-bit clean pipe to send its data.
What ssh does on its own to authorize connections is of no concern to
rsync.
Matt,
Thanks very much. However, for several reasons, I cannot apply that
trick in my case. Apart from those reasons, there is no X server on
middle or target at all. Moreover, which password-prompting program
should I use? middle is an OpenBSD machine. And what should I put in
$DISPLAY?
Wow! Dude! This is the most comprehensive, user-friendly, nice,
knowledgeable answer I have ever received. Thanks very much! That
answers everything.
I understand completely that it's not rsync's job to handle ssh password
prompts, however, isn't it the first password prompt handled by rsync?
Matt McCutchen wrote:
Martin Schröder's suggestion of ssh-agent might be better in the long
term or if the X business doesn't work, but I got the impression you
didn't want to set up any kind of special SSH authentication.
Yes, that is precisely the point.
There is a FAQ section (which I
17 matches
Mail list logo
