On Tue, Jul 10, 2001 at 02:24:57AM -0700, Ben Escoto wrote:
About two weeks ago I asked about a way to use rsync to backup (I
wanted to make something in-between a mirror and an incremental
backup). I wrote a preliminary version of a program that does this
(see
DD == Dave Dykstra [EMAIL PROTECTED]
wrote the following on Tue, 10 Jul 2001 10:34:53 -0500
DD All that rsync uses ssh for is to open a bi-directional data
DD pipe and run a command (another rsync program) on the remote
DD side. It then ignores ssh (or rsh, the default) and does its
I see there is quite a bit discussion on the list about rsync hanging on a
variety of conditions, one of which I seem to be having. We use rsync to
update remote servers over night. Each system syncs with a master server
holding around 4.0 gig of data. Normally there is very little change on
On Tue, Jul 10, 2001 at 10:58:21AM -0700, Ben Escoto wrote:
DD == Dave Dykstra [EMAIL PROTECTED]
wrote the following on Tue, 10 Jul 2001 10:34:53 -0500
DD All that rsync uses ssh for is to open a bi-directional data
DD pipe and run a command (another rsync program) on the remote
DD
There are 2 patches on this mailing list that fix the 2.4.6 hangs for
me. Check the archives and you should be able to find them.
I hope to see a 2.4.7 out soon that includes some or all of those hang
fixes.
eric
Steve Ladendorf wrote:
I see there is quite a bit discussion on the list
On Tue, 10 Jul 2001, Steve Ladendorf wrote:
Is there something I'm doing wrong? What can I do to prevent rsync from
hanging all the time??
If you avoid using -v, that can help rsync not to hang. However, a
better fix is to apply this patch:
Hi Wayne,
On Tue, Jul 10, 2001 at 01:59:22PM -0700, Wayne Davison wrote:
http://www.clari.net/~wayne/rsync-nohang1.patch
http://www.clari.net/~wayne/rsync-nohang2.patch
Are these to be applied against the stock 2.4.6? In particular, the second
patch does not apply cleanly against
A month of sundays ago Steve Ladendorf wrote:
variety of conditions, one of which I seem to be having. We use rsync to
update remote servers over night. Each system syncs with a master server
holding around 4.0 gig of data. Normally there is very little change on
the master so rsync only
On Tue, 26 Jun 2001, Martin Pool wrote:
On 25 Jun 2001, Wayne Davison [EMAIL PROTECTED] wrote:
I was wondering if the protocol should be updated to avoid ever
assuming that an EOF on the socket was OK. The only case I know of
where this allowed is when we're listing modules from an rsync
On Tue, Jul 10, 2001 at 03:19:51PM -0700, Wayne Davison wrote:
They will apply to stock 2.4.6 with offsets (but no fuzz), if you so
desire. They were created from the CVS version, though.
OK.
The nohang1 patch is already incorporated into the CVS version, so it is
the only one that should
On Tue, Jul 10, 2001 at 04:13:11PM -0700, Jos Backus wrote:
I'm using the same CVS server. I think my problem is that I applied your
rsync-nohang.patch first, whereas I should only be applying
rsync-nohang2.patch against the current CVS sources. Correct?
To answer my own question: yes.
11 matches
Mail list logo
