search for: ukf

I have a rsync server set up on a win2k server and a win xp pro computer is my client. It's working very well doing the anonymous transfers. However, I've tried setting up a password file and not having any success. rsyncd.conf on my server: use chroot = false strict modes = false hosts allow = * [serverbu] auth users = user path = c:/serverbu read only = no list = no secrets file =

On May 14, 6:26am, maxb@ukf.net (Max Bowsher) wrote: -- Subject: rsync digest, Vol 1 #717 - 12 msgs > > + After thinking about it a bit more I'm somewhat inclined to call it a > + bug in Cygwin and try to get them to fix it. > > Well, you could, but I'd much prefer it if you didn't :-) > I gues...

The problem is caused because rsync does not close its sockets, and WinSock is a quite strict on this. The solution is to shutdown and close the fd. This is a 5-minute hack I've done to fix the obvious occurrences of the problem. It might be better to extend rsyncs cleanup functions for this, but here it is anyway to alert people to the problem and its fix. Max. BEGIN PATCH diff -mru

Hi. On the one hand, I don't want to annoy anyone with repeated emails :-), but on the other, I would like to know the chances of the patch making it in to 2.5.6. Even if the answer is 'Maybe - too busy to think about it right now', I will be satisfied, but if I need to revise it before it can be considered, I would like to know that. Max.

Hello? Concerns were raised about the action of shutdown() on Unices - I replied with evidence suggesting that this would not be a problem. I have not heard anything since. If this has to be held over to 2.6.0, fair enough - but please tell me whether itjust needs time, or me to go and fix something??? Thanks Max. BEGIN PATCH diff -mru rsync-2.5.5/clientserver.c

There is an rsync/popt/config.log in CVS - presumably an accidental "cvs add". Max.