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 ps aux shows nothing more than bash running, how can I be certain rsyncd is stopped? I had updated the server to File-RsyncP-0.68 when I started this last week. I think that is current enough? Thanks again, Jim On 12/14/06, Jason Hughes <[EMAIL PROTECTED]> wrote: > 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 server's > File::RsyncP in cpan. > > JH > > > Jim McNamara wrote: > > And the new error makes even less sense to me, > > > > Contents of file /var/lib/backuppc/pc/mas90-server/XferLOG.bad.z, > > modified 2006-12-14 22:12:40 > > > > Connected to mas90-server:873, remote version 29 > > Negotiated protocol version 26 > > Error connecting to module UPC at mas90-server:873: chroot failed > > Got fatal error during xfer (chroot failed) > > Backup aborted (chroot failed) > > > > ???????? > > > > I don't have chroot enabled anymore, it is completely absent from the > > rsyncd.conf on the winbox. > > > > > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
