Re: [BackupPC-users] Using linux rsync to backup Windows clients

2007-11-13 Thread Rob Owens
Bill B. wrote: > On Nov 12, 2007 5:55 AM, Rob Owens <[EMAIL PROTECTED]> wrote: > >> Maybe try starting with the most basic command for troubleshooting: >> >> rsync 10.10.1.247:: > > > That doesn't work from either machine. > > I think I'm going to do a test install of debian, just to see if th

Re: [BackupPC-users] Using linux rsync to backup Windows clients

2007-11-12 Thread Bill B.
On Nov 12, 2007 5:55 AM, Rob Owens <[EMAIL PROTECTED]> wrote: > Maybe try starting with the most basic command for troubleshooting: > > rsync 10.10.1.247:: That doesn't work from either machine. I think I'm going to do a test install of debian, just to see if the behavior is the same. I compil

Re: [BackupPC-users] Using linux rsync to backup Windows clients

2007-11-12 Thread Rob Owens
Maybe try starting with the most basic command for troubleshooting: rsync 10.10.1.247:: That should list all the modules that are available. If it shows the "docs" module from your CentOS machine, then maybe there's something in your previously-used syntax that CentOS doesn't like. (Perhaps it

Re: [BackupPC-users] Using linux rsync to backup Windows clients

2007-11-09 Thread Bill B.
> 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. Agreed. However, for Centos 4.4 the compiled version of rsync (2.3.6) doesn't seem to play nice when using ::/path. [EMAIL PROTEC

Re: [BackupPC-users] Using linux rsync to backup Windows clients

2007-11-09 Thread Les Mikesell
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 defaul

Re: [BackupPC-users] Using linux rsync to backup Windows clients

2007-11-09 Thread Bill B.
Well, rsync is not ssh. These days most rsync clients default to ssh transport, but rsync itself is it's own protocol. 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.

Re: [BackupPC-users] Using linux rsync to backup Windows clients

2007-11-09 Thread Gene Horodecki
Someone correct me if I'm wrong here, but it sounds like maybe you're confusing rsyncd and rsync. rsyncd will be governed to a certain extent by rsynd.conf and access the shares accordingly. A rsyncd connection happens through a special rsyncd port (I think 843 by default). The rsync connection

[BackupPC-users] Using linux rsync to backup Windows clients

2007-11-09 Thread Bill B.
Hello, I've been trying to figure out how to use the windows rsyncd package from the backuppc site. Everything is installed fine, and if I connect using rsync from my Mac laptop (OSX), rsync works as expected. If, however, I connect from a linux based machine, it tries to use ssh as the default