On Thu 11 Dec 2008, Peter Palfrader wrote: > Package: rsync > Version: 3.0.3-2~bpo40+1 > Severity: important > > Hi, > > per request of mirroradm I had installed rsync 3.0.3-2~bpo40+1 on > kassia.debian.org. > > This resulted in stable rsync clients (2.6.9-2etch2) no longer being > able to access rsync shares:
I've been wondering what to say about this, and I've sort of given up... There were some problems in the first 3.0.0 and 3.0.1 versions when transferring large files with an older client, but that shouldn't be an issue anymore. I've not had any problems between different versions myself, and a quick test shows that at least ftp.nl.debian.org is also using a 3.0.x version rsync daemon, and apparently doesn't have problems. Hence I'm wondering whether the backport doesn't have a problem. Perhaps having tcpdumps from both ends will help to show what exactly goes wrong, seeing how both ends now claim "Connection reset by peer", only one is right, you'd expect... There isn't some inetd-type thing that wraps accesses to the rsync daemon, that may be screwing things up? Paul -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
