Remote Assistance

[Travis Fraser]

On Tue, 2005-07-05 at 12:58 -0500, Les Mikesell wrote:
> On Tue, 2005-07-05 at 07:25, Travis Fraser wrote:
> > > > > 
> > > > > Are you saying that you are running a remote rsync started by cygwin
> > > > > sshd?  I've been trying to get that to work for years.  Or are you
> > > > > port-forwarding through ssh to rsync in daemon mode?
> > > > Hi,
> > > > 
> > > > I have been doing the former, but with small amounts of data no more
> > > > than 20 or 30 MB. I have discovered though, that often the transfer
> > > > dies. I can't figure out if it is the amount of data, or what.
> > > 
> > > It's a bug and the time when it stalls seems to be unpredictable.
> > > Running rsync in daemon mode will work, and if necessary you can
> > > use ssh port-forwarding to connect to it.  It's odd because about
> > > everything else works as you would expect under sshd.
> 
> > Are there any known work-arounds other than running rsync in daemon
> > mode?
> 
> I'm not aware of any - and I just updated my Cygwin install to make sure
> the bug is still there. It does work the other direction - that is, if
> you issue the 'rsync -essh ...' command on the Cygwin/Windows box with
> the remote side running Linux/unix.  It can copy either direction when
> invoked this way 

I was trying to pull from the server using a ssh public key on the
client. This was an experimental alternative to using smbclient to pull
backups using backuppc (which works great BTW, just no encryption and no
rsync).

> - the specific bug has to do with the cygwin rsync
> running under sshd.  Just guessing, I'd say something is wrong in
> the buffering and both sides end up waiting for each other.

-- 
Travis Fraser <travis at snowpatch.net>