On Fri, 22 Jun 2001, Dave Dykstra wrote:
> > The default value of the non-blocking IO is not
> > affected by this change -- instead rsync only sets non-blocking IO by
> > default if the RSYNC_RSH value is "rsh" or (if remsh is around) "remsh".
>
> This is a very tricky thing to do right, and proba
On Fri, Jun 22, 2001 at 02:30:08PM -0700, Adam McKenna wrote:
> OK, I'll try it. Do you think upgrading to OpenSSH 2.9p2 would help
> anything?
I'm not aware of any differences between the versions that could affect
this problem.
- Dave Dykstra
On Fri, Jun 22, 2001 at 04:09:19PM -0500, Dave Dykstra wrote:
> Those versions are recent enough. Try Wayne Davison's nohang patch at
> http://www.clari.net/~wayne/rsync-nohang.patch
>
> Presumably the transfer is hanging for a period of time before it times out.
> If Wayne's patch doesn't f
On Fri, Jun 22, 2001 at 01:58:37PM -0700, Adam McKenna wrote:
> On Fri, Jun 22, 2001 at 03:56:45PM -0500, Dave Dykstra wrote:
> > Rsync puts a heavy strain on TCP implementations because of the serious
> > pipelining it does, and often reveals bugs in them.
> >
> > Are you using rsync 2.4.6? The
On Fri, Jun 22, 2001 at 03:56:45PM -0500, Dave Dykstra wrote:
> Rsync puts a heavy strain on TCP implementations because of the serious
> pipelining it does, and often reveals bugs in them.
>
> Are you using rsync 2.4.6? There were some serious problems with rsync
> causing ssh to hang in the e
On Fri, Jun 22, 2001 at 11:11:30AM -0700, Adam McKenna wrote:
> On Fri, Jun 22, 2001 at 12:39:22PM -0500, Dave Dykstra wrote:
> > That level of the network is completely outside of rsync's control; if
> > you're using -e ssh, do you have problems when you use ssh by itself?
>
> I understand that
On Fri, Jun 22, 2001 at 11:02:53AM -0700, Wayne Davison wrote:
> Here's a patch that adds the --with-rsh option to configure. It allows
> the default remote shell to be set to ssh, or any other value that the
> configurator desires.
A similar change was proposed a few months ago and rejected.
On Fri, Jun 22, 2001 at 12:39:22PM -0500, Dave Dykstra wrote:
> That level of the network is completely outside of rsync's control; if
> you're using -e ssh, do you have problems when you use ssh by itself?
I understand that -- yes, I'm using -e ssh and ssh works fine by itself. My
rationale her
Dave Dykstra [[EMAIL PROTECTED]]
> That level of the network is completely outside of rsync's control; if
> you're using -e ssh, do you have problems when you use ssh by itself?
Note that while rsync is certainly above this level of the network,
asymmetric routes are notorious for causing signif
Here's a patch that adds the --with-rsh option to configure. It allows
the default remote shell to be set to ssh, or any other value that the
configurator desires. The default value of the non-blocking IO is not
affected by this change -- instead rsync only sets non-blocking IO by
default if the
That level of the network is completely outside of rsync's control; if
you're using -e ssh, do you have problems when you use ssh by itself?
- Dave Dykstra
On Thu, Jun 21, 2001 at 12:29:13PM -0700, Adam McKenna wrote:
> I have a reproducible problem with rsync --
>
> I have two systems, on in
It works if you explicitly set 'uid = root', I just tested it.
Note in the man page under --numeric-ids that if you aren't using
'use chroot = no' that a module has to use direct numeric id mapping,
it can't translate user ids based on login name.
- Dave Dykstra
On Fri, Jun 22, 2001 at 10:38:49
Hello,
I'm using rsync to connect to an rsync server on a remote machine.
rsync on the remote machine is set up as a daemon and utilizes the
rsync.conf configuration file for granting access, defining accessible
directories, etc. based on modules. Also in the rsync.conf file are the
uid and gid
I have been testing this patch in a duplicate of our production environment, for a
week now. With the patch, the runs complete. I'm handling
86756263K in 1816688 files (at last count) average 47K files (ranging up to about
.5G). It seems to solve the problems. I think it constitutes rsync
Thanks for committing the crash-bug fix, Martin.
I'm curious if you have any comments on my fixes for the 2 protocol-hangs
I discovered? The most common problem that people encounter is the bug I
fixed second, which is fixed by a very simple patch:
Index: main.c
--- main.c 29 May 2001 14:3
15 matches
Mail list logo
