On Thu, Jan 04, 2001 at 12:12:43PM +1000, [EMAIL PROTECTED] wrote:
> Dave_Dykstra_ wrote:
> > Because of the piplined nature of the rsync implementation and the
> > back-and-forth nature of the rsync protocol, rsync stresses many TCP
> > implementations. No one else has mentioned a problem with F
Dave_Dykstra_ wrote:
> Because of the piplined nature of the rsync implementation and the
> back-and-forth nature of the rsync protocol, rsync stresses many TCP
> implementations. No one else has mentioned a problem with FreeSwan, but I
> suspect a bug with it. You should at least run "netstat"
On Fri, Dec 29, 2000 at 09:19:52AM +1000, Bob Hepple wrote:
> "Peter T. Breuer" wrote:
> >
> > Sounds like the ssh pipes/socketpairs problem. Are you running over
> > ssh? If so a solution is to recompile ssh.
> >
>
> No, plain ole' rsh. But I get the same result with ssh.
>
> Before I posted
"Peter T. Breuer" wrote:
>
> Sounds like the ssh pipes/socketpairs problem. Are you running over
> ssh? If so a solution is to recompile ssh.
>
No, plain ole' rsh. But I get the same result with ssh.
Before I posted I noticed previous similar problems in this list (but
not with FreeSwan, just
"A month of sundays ago [EMAIL PROTECTED] wrote:"
> Using FreeSwan 1.5 to connect 2 networks and rsync 2.4.6 to transport
> files between 2 Linux boxes (RH6.1/kernel 2.2.17 and 2.2.14)
>
> On small transfers of a couple of dozen files, all is sweet. When a lot
> of files are involved, it hangs fo
Using FreeSwan 1.5 to connect 2 networks and rsync 2.4.6 to transport
files between 2 Linux boxes (RH6.1/kernel 2.2.17 and 2.2.14)
On small transfers of a couple of dozen files, all is sweet. When a lot
of files are involved, it hangs forever at varying places. rsync -vvv
shows nothing interestin
