Okay, I'm feeling kinda foolish now. All the information you guys
gave me seems very straightforward and helpful, as do the rsync &
rsyncd.conf man pages. But I can't seem to get rsyncd working, though
I'm pretty sure it's just me doing something dumb. It keeps failing
with "inet connect: Connection refused" (yes, the XP firewall is off).
I believe the only thing I've changed in config.pl was adding
'--one-file-system' to RsyncArgs. Here is my current <hostname>.pl:
$Conf{XferMethod} = 'rsyncd';
$Conf{RsyncShareName} = ['cyghome'];
$Conf{RsyncdUserName} = '<user>';
$Conf{RsyncdPasswd} = '<password>';
$Conf{RsyncdAuthRequired} = 1;
And here is my rsyncd.conf on the windows box (though I confess I'm
not entirely clear on where it's expected to go, I've tried /etc and /
under cygwin, as well as c:\):
use chroot = false
max connections = 10
pid file = c:/rsyncd/rsyncd.pid
lock file = c:/rsyncd/rsyncd.lock
log file = c:/rsyncd/rsyncd.log
[cyghome]
path = c:/cygwin/home
comment = C:\cygwin\home
strict modes = false
auth users = <user>
secrets file = c:/rsyncd/rsyncd.secrets
hosts allow = <backuppc_server_ip>
read only = false
list = false
As you can see, I'm only attempting to backup /home under cygwin for
now, mostly for testing purposes, to keep it simple. I've also tried
using nix/cygwin style paths (which made sense to me, since rsync's
being run from within cygwin) like so:
use chroot = false
max connections = 10
pid file = /var/run/rsyncd.pid
lock file = /var/run/rsyncd.lock
log file = /var/log/rsyncd.log
[cyghome]
path = /home
comment = C:\cygwin\home
strict modes = false
auth users = <user>
secrets file = /etc/rsyncd.secrets
hosts allow = <backuppc_server_ip>
read only = false
list = false
And yes, I of course made sure the secrets file was always where the
conf said it was, and that all of the referenced directories existed.
The rsyncd.secrets file consists only of a single line reading
"<user>:<password>", which I created with vi in cygwin (unix style
text files). I also tried changing the port number to 1873 (in both
rsyncd.conf, and <hostname>.pl), in case it was an issue of
permissions to open a port below 1024.
Finally, just to help me understand what should be happening ... when
the rsync client (the backuppc server, correct?) attempts to spawn an
rsync daemon on the backuppc client, it's still starting with a
remote-shell transport (rsh/ssh) to pass the command to initiate the
rsync daemon, and it then has an rsync client contact the newly
spawned rsync daemon directly (and I assume then shuts down the
remote-shell transport?), correct? If not, how is it spawning the
daemon?
Thanks so much!
Tom
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
