openssh 3.1 and rsync dont work

Dave Dykstra dwd at
Fri May 10 10:19:21 EST 2002

I took a look in the rsync CVS; the change to rsync that (unintentionally)
prevented this problem was put into version 2.4.6 by Andrew Tridgell:

I'm still concerned that we might run into a problem with ignored signals
being inherited by child programs, however, and I think maybe we should put
in some preventative code.  SIGPIPE is currently the only signal that is
completely ignored.  However, the current signal handler for SIGCHLD has
caused another problem:

and we may end up ignoring SIGCHLD again to fix this, I'm not sure.

- Dave Dykstra

On Thu, May 09, 2002 at 04:13:45PM -0400, Jim Ogilvie wrote:
> When we first switched to openssh 3.1 with rsync 2.3.1 we had the same
> error from ssh-rand-helper. But after switching to rsync 2.5.5rc1 the
> problem went away. (this is on AIX).
> --
> Jim Ogilvie
> On Thu, 9 May 2002 09:34:57, Dave Dykstra wrote:
> > I want to fix this in rsync too.  I developed what I think is a good fix
> > and now I'm trying to reproduce the problem so I can test whether or not
> > the fix worked.  The trouble is, I can't reproduce it with "-e ssh" even
> > though I'm sure I'm running openssh 3.1p1 on solaris where it's running
> the
> > ssh-rand-helper.  truss doesn't show rsync setting SIGCHLD to SIG_IGN.  I
> > found that there is one place in the rsync 2.5.5 code that sets SIGCHLD
> to
> > SIG_IGN, but it appears to only be in rsync --daemon mode, and it
> wouldn't
> > call ssh from there.
> >
> > What version of rsync did you have the problem in, and what was the
> command
> > line you used?
> > - Dave Dykstra
> -- 
> To unsubscribe or change options:
> Before posting, read:

More information about the rsync mailing list