Hi Libor!
Thanks for your hint!
In fact using rsync via ssh as workaround *does work for me*, too.
This indeed adds an extra performance penalty for the SSH tunneling, but
in my final setup SSH will be required anyways.
In fact this issue seems to occur mainly with slow rsync servers like
N
Utter silence!
socnt01:~ # ssh [EMAIL PROTECTED] 'missing-rsync 2>&1'
socnt01:~ # ssh [EMAIL PROTECTED] 'echo testing >&2'
socnt01:~ #
The key in authorized_keys is completely vanilla, as generated by
ssh-keygen. Here's the last few characters:
HDX9YgmYKiYyOvQMDKpeJXs= [EMAIL PROTECTED]
On Thu, Jan 13, 2005 at 08:17:42PM +, Nigel Gilbert wrote:
> Interestingly, when I use ssh to execute a non-existent command on the
> remote machine, no error message is returned
Fascinating. Perhaps your ssh isn't returning the stderr output? Try
these commands:
ssh [EMAIL PROTECTED] '
Interestingly, when I use ssh to execute a non-existent command on the
remote machine, no error message is returned (BTW, it is not clear in
your email below whether you mean by "Your shell" the shell on the
local machine - which certainly will complain if asked to execute a
non-existent comman
On Thu, Jan 13, 2005 at 05:20:51PM +, Nigel Gilbert wrote:
> This might be thought to be a bug or a missing feature in rsync; rsync
> could have produced a more comprehensible error message.
Your shell should have told you about the command problem -- for
instance, I see this trying to run th
I'm sorry about the rather confusing error report - I wanted to be
brief and to the point, but ended up leaving out important detail.
I was running a script. The missing "" were an artefact of me
debugging the script by copy and pasting the rsync line as the argument
to an echo command, and fo
