BackupPC-users

Re: [BackupPC-users] The dread "Unable to read 4 bytes" / "Read EOF: Connection reset by peer"

2010-05-11 13:46:54
Subject: Re: [BackupPC-users] The dread "Unable to read 4 bytes" / "Read EOF: Connection reset by peer"
From: Les Mikesell <lesmikesell AT gmail DOT com>
To: backuppc-users AT lists.sourceforge DOT net
Date: Tue, 11 May 2010 12:45:20 -0500
On 5/11/2010 12:26 PM, Nick Bright wrote:
> On 5/11/2010 9:53 AM, Les Mikesell wrote:
>> On 5/10/2010 8:14 PM, Nick Bright wrote:
>>
>>> Let me start off by saying this: I know what I'm doing.
>>>
>>>
>> [...]
>>
>>> full backup started for directory / (baseline backup #259)
>>> started full dump, share=/
>>> Running: /usr/bin/ssh -q -x -l root TargetServer /usr/bin/rsync --server
>>> --sender --numeric-ids --perms --owner --group -D --links --hard-links
>>> --times --block-size=2048 --recursive --port=38271 --ignore-times . /
>>>
>> What does --port=38271 mean here?  Isn't that supposed to be used for
>> standalone rsyncd, not over ssh?
>>
>>
> Thank you for taking the time to reply.
>
> It's the port that SSHD is listening on. I had been stripping that out
> because the guy that runs the target server is a little paranoid about
> his SSH access.

In that case, shouldn't it be in the ssh arguments, not part of the 
rsync command passed to the remote?  I don't see how this would connect 
at all.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com



------------------------------------------------------------------------------

_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

<Prev in Thread] Current Thread [Next in Thread>