From: <cba...@us...> - 2003-04-17 09:48:29
|
> I've got everything working from a single directory, and running as an > autostart service available from the control panel. This doesn't cygwin > install. I'm not sure about the cygwin DLL issue - having *any* multiple > DLLs is usually a bad thing, so I'll just document it in the readme. > > The cygrunsrv.exe file doesn't require any additional DLLs. I did have to > change the win32 permissions to restrict the permissions of the directory > and the various rsyncd conf files in order to get rsync to work properly. > I'll document this as well. Cool! > One thing I am curious about is whether or not my setup will work on > anything other than Win2K. Beyond the cygwin DLL there are dependencies on > some system DLLs. I'll test on XP, but I don't have any other platforms to > test on. Same for me. I have a virgin (no cygwin) WinXP machine I can try it on, but I don't have access to NT, Win98 etc. Other users can submit feedback for these platforms. If you haven't done so already you should also add: # Only allow connections from the BackupPC server. # Replace IP address with the IP address of your BackupPC server. hosts allow = 192.168.1.10 to rsyncd.conf so that only connections from the BackupPC server are allowed. Rsyncd's password (which uses a random challenge/hash response, so no plain text password is sent) plus the host restriction makes the rsync setup a lot more secure than sharing the C drive and using SMB. (I'm not sure if SMB uses plain text passwords - looking at the smbclient source shows that it supports both plain text and encrypted passwords, depending upon the server capabilities.) However in either case the backup traffic itself is not encrypted. I've been unable to get rsync to work with ssh on cygwin, although it works fine on linux. Craig |