On Tue, 11 May 2010 12:26:47 -0500, Nick Bright <o...@valnet.net> 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.
Can you run:
/usr/bin/ssh -q -x -l root TargetServer /usr/bin/rsync --version
And get a proper output? If not then something is up with the remote
server. You mention paranoia of the remote server admin -- is it possible
that in his authorized_keys file he's limited the command that can be run
via that key? If so, is it correct. That's a huge recipe for ssh disaster
in my experience w/ backuppc.
--
--------------------------------------------------------
Joshua Malone Systems Administrator
(jmal...@nrao.edu) NRAO Charlottesville
434-296-0263 www.cv.nrao.edu
434-249-5699 (mobile)
BOFH excuse #360:
Your parity check is overdrawn and you're out of cache.
--------------------------------------------------------
------------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
