Bill B. wrote:
> Well, rsync is not ssh. These days most rsync clients default to ssh
> transport, but rsync itself is it's own protocol.
If you are using a command line rsync to connect, you specify host:/path
for an ssh connection, host::/path for the standalone protocol. It's
not a default.
> I don't want to
> deal with ssh under cygwin, so I'm opting not to use it.
> Unfortunately, this is proving to be an issue.
>
> I have the daemon (rsyncd) running on the windows host. I am then
> connecting from the backuppc server (linux machine) and running rsync
> as instructed in the windows howto. Since the writing of the backuppc
> Windows rsyncd howto, the rsync client has undergone some changes to a
> point where it now defaults to ssh on most linux platforms. As I
> showed in my examples, the rsync command works great from an OSX
> client, and in fact they're the same rsync version, 2.3.6.
>
> I know what rsync and rsyncd are. I don't know how to get a more
> recent version of rsync on a linux machine to talk nicely to the
> bundled rsyncd on the backuppc page. :)
In backuppc you need to set $Conf{XferMethod} to 'rsync' for hosts where
you use ssh, and to 'rsyncd' to connect to the standalone daemon.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
