On Tue 16 Dec 2008, Peter Palfrader wrote: > On Tue, 16 Dec 2008, Paul Slootman wrote: > > > > 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: > > > 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... > > tcpdumping kassia is possible, breaking it to possibly broken versions > not so much (given that it's security, ftp.d.o, and eu-syncproxy). I'll > try to reproduce the issue some place else.
You could try installing it in parallel (i.e. grab the /usr/bin/rsync binary out of the .deb and stick that as /usr/bin/rsync-3.0), and let it listen on a different port number. > > There isn't some inetd-type thing that wraps accesses to the rsync > > daemon, that may be screwing things up? > > Well, it is running out of xinetd, but that doesn't change between 2.6.9 > and 3.0.3. Yes, but it may interact in some way that interferes with the new version! Why not let rsync run as a daemon? IMHO that's the best way... Paul -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
