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\cygrunsrv.exe", which seems very wrong for rsync?
More brilliance, the service claims to stop within 2 seconds of running it, which should not be the case for either cygrunsrv or rsync. Thanks yet again, Jim On 12/14/06, Jason Hughes <[EMAIL PROTECTED]> wrote: > 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. > cygrunsrv -I rsyncd -d > The definitive way to tell if a service is running is to open > Settings/ControlPanel/AdministrativeTools/Services and scroll down until > you see 'rsyncd' and a status next to it. Right click on it to manually > start/stop the service. This definitely works. > > Re: File::RsyncP, I think that is the most recent version. > > Hope this helps, > JH > > Jim McNamara wrote: > > 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 BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
