On 31 January 2012 22:14, Les Mikesell lesmikesell@gmail.com wrote:
On Tue, Jan 31, 2012 at 4:01 PM, m.roth@5-cent.us wrote:
On Tue, Jan 31, 2012 at 3:14 PM, Ljubomir Ljubojevic office@plnet.rs wrote:
On 01/31/2012 09:47 PM, Les Mikesell wrote:
No, I'm trying to have rsync make an outbound connection over ssh from the rescue environment and getting what looks like an argument error from ssh. Ssh itself works and I can connect to the same target if I run it directly, and the exact same rsync command lines work from a normal host. Either rsync isn't setting up the remote command right, or ssh isn't allowing it and giving a bad error message.
There was a buggy version of rsync that did this. It wasn't initialising the ssh session properly from my email a while ago:
On Tue, 23 Aug 2011, Ned Slider wrote:
On 23/08/11 12:35, Michael Simpson wrote:
Hello
Is anyone else having problems on 5.6 using the new rsync from the CR repo I have only managed to get rsync (called from the cli) working again after downgrading it to the previous 2.x release as the newer version was just spitting out the ssh usage information and failing. This server is stock i386 with just the CR as an extra repo.
regards
mike
Known issue I'm guessing:
https://bugzilla.redhat.com/show_bug.cgi?id=724041
which was fixed nearly a month ago.
So instead of saying nearly a month ago how about we we say it was only released 20 days ago. BZ says it was released 03 Aug 11.
If this is your issue, try appending username@host like so:
rsync user@host:/
as a workaround, but I'm not sure why CentOS is still shipping an old broken version?
Umm, maybe because upstream shipped rsync-3.0.6-4.el5.i386.rpm with 5.7 and the rsync-3.0.6-4.el5_7.1.i386.rpm has not made it to CentOS yet.
Remember that bug for bug compatibility thing. :-)
Patience is a virtue.
Regards,