Hi all,
Has the "deflate on token returned" bug (apparently still present in
2.5.6) when transferring large files been fixed by chance?
http://marc.theaimsgroup.com/?l=rsync&m=101777555820384&w=2
I'm using zlib-1.1.3. The bug does not occur when not using -z option
> If it's what I suspect, answer these questions:
>
> Are all the keys different? (You have to say "yes" here.)
Yes, should have thought to make that clear initially.
> Are you using an ssh-agent at the calling end? ("You want "no" here,
> and a "-i keyfile" in the ssh call.)
Hi all,
I've asked this question before, but I was never able to fix the problem,
and now it's back again and I'd like to try and resolve it.
I have an authorized_keys file with about twenty keys, most of which are
prefaced with command="/usr/bin/rsync ...". If I put my host key at the
top of th
> We have had situations where -v appeared to cause a hang, although I thought
> those had been fixed. Try without that.
No difference.
> Try with trial & error to eliminate particular files. I once found a
> single 80 byte file that could hang rcp every time, we assumed because
> of some bug
> Try this patch, so far hanging does not happen anymore.
>
> http://www.clari.net/~wayne/rsync-nohang1.patch
Applied the patch, upgraded both sides, and same thing. I'm not so sure
it's an rsync thing anymore, but have no ideas what the problem could
possibly be.
Thanks,
Dave
> I'm not aware of any protocol differences. Can you be more specific?
> Try to give us some simple steps to reproduce it if you can.
Actually, I screwed up. The remote side had quite an old version of rsync.
Upgrading to 2.4.6 fixed the protocol problems but hasn't fixed the hang
problem.
It'
Hi all,
rsync-2.4.6 has been running for quite a while with no problems, until
about a week ago when for some reason it blocked on the same host ever
time.
I use it to backup about thirty hosts to my backup server, but for some
reason it's illiciting that blocking bug that some people experienc
> Oh. Can you send me an "ssh -v" transcript showing the behaviour?
Cameron, I think I made a mistake. Not exactly sure yet, but I rearranged
the order of the keys causing the incorrect matching, and it's working. I
believe there may have been a 'z' on the sending side but not the rsync on
the r
> | This sounds more like an ssh bug; I would try taking the report to
> | their mailing lists.
>
> Well... "It's a feature."
>
> Well, anyway, it's documented behaviour. Ssh will try all the keys, even if you
> hand it the -i flag to say "here's the key I want, dumbo!"
>
> Solution: disable y
Hi all,
I'm using command= in my authorized_keys file in conjunction with rsync,
but for some reason it's matching the wrong key. It also seems arbitrary.
On the local side, I'm using "rsync -avze 'ssh -i key' files/ host:/path"
and on the remote side I'm using:
command="/usr/bin/rsync --server
10 matches
Mail list logo
