rsyncd is listed there as you expected, but it had no status when I
saw it. I told it to start, and it produced some garbage about
"service started then stopped" and goes on about some services like
logging having that as standard. In any case, the path to executable
field says "C:\cygwin\bin\cygru
From what I can tell, all that does is insert and remove registry
entries from the services list in Windows. cygrunsrv has a separate
command for stopping and starting services, and I'm not sure (without
testing it) if removing will actually stop the service as well.
The definitive way to tel
I used:
cygrunsrv --remove rsyncd
and then checked with:
cygrunsrv --list
which only showed sshd running. I still get the chroot error, and it
seems that rsync not running should produce an error long before
anything about chroot. Since cygwin shell seems to be crap (no
/etc/init.d/rsyncd) and p
You may need to stop/restart the rsyncd service to make it read the
rsyncd.conf file on windows.
I wanted to mention that there was some bug that I ran into (you're not
seeing it yet) when the backuppc was using protocol version 26 and
windows running rsyncd. You might want to update the serve
It was a mixture of both! Stealing the configs from a pure linux rsync
backuppc, I had:
$Conf{RsyncShareName} = '/UPC';
Which I now changed to
$Conf{RsyncShareName} = 'UPC';
And the new error makes even less sense to me,
Contents of file /var/lib/backuppc/pc/mas90-server/XferLOG.bad.z,
modified
On Thursday 14 December 2006 21:50, Jim McNamara wrote:
> [UPC]
> /cygdrive/f/UPC
> hosts allow = 192.168.2.1
> strict modes = false
> Connected to mas90-server:873, remote version 29
> Negotiated protocol version 26
> Error connecting to module /UPC/ at mas90-server:873: Unknown module
> '/UPC/'
I tried rsyncd, and still encounter problems. Fortunately they are
different problems, so hopefully there is a known solution.
Here is the current rsyncd.conf on the windows box:
[UPC]
/cygdrive/f/UPC
hosts allow = 192.168.2.1
strict modes = false
[apps]
/cygdrive/g/apps
hosts allow = 192.168.2.
I got the impression that this problem may have been fixed in a newer
version of backuppc, would upgrading help?
I'll try reconfiguring backuppc to do rsyncd instead of rsync if not.
Thanks,
Jim
On 12/12/06, Carl Wilhelm Soderstrom <[EMAIL PROTECTED]> wrote:
> On 12/11 09:43 , Jim McNamara wrote
On 12/11 09:43 , Jim McNamara wrote:
> I am in the process of switching a backup from using smbclient to
> rsync, as it is taking greater than 72 hours to perform a backup. The
> backuppc is running debian stable, backuppc v 2.1.1, and the client
> machine is windows server 2003 with cygwin on it.
Hello all!
I found some mails in the archive that relates to this problem, but
what seemed to be the solution didn't work for me. I'd like to show
what's happening, and hope to get some input on what the problem is.
Here is the info I found in the archives:
http://sourceforge.net/mailarchive/mes
10 matches
Mail list logo
