All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: anton@linuxcare.com.au (Anton Blanchard)
Cc: linux-kernel@vger.kernel.org
Subject: Re: rsync over ssh on 2.4.2 to 2.2.18
Date: Tue, 27 Feb 2001 16:48:21 +0000 (GMT)	[thread overview]
Message-ID: <200102271648.f1RGmLr08116@brick.arm.linux.org.uk> (raw)
In-Reply-To: <20010228001800.C2207@linuxcare.com> from "Anton Blanchard" at Feb 28, 2001 12:18:00 AM

Anton Blanchard writes:
> > I'm seeing odd behaviour with rsync over ssh between two x86 machines -
> > one if the is an UP PIII (Katmai) running 2.4.2 (isdn-gw) and the other
> > is an UP Pentium 75-200 (pilt-gw) running 2.2.15pre13 with some custom
> > serial driver hacks (for running Amplicon cards with their ISA interrupt-
> > sharing scheme).
> 
> What version of ssh are you using? Older versions would use blocking IO
> which would result in deadlocks (and angry emails wrongly blaming rsync :)

Note that I proved that it was sitting in select(), and therefore can't be
blocking.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2001-02-27 16:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 10:02 rsync over ssh on 2.4.2 to 2.2.18 Russell King
2001-02-27 10:18 ` Rasmus Andersen
2001-02-27 10:58   ` bert hubert
2001-02-27 10:49 ` David S. Miller
2001-02-27 19:46   ` Russell King
2001-02-27 13:18 ` Anton Blanchard
2001-02-27 16:48   ` Russell King [this message]
2001-02-27 20:35 ` kuznet
2001-02-27 20:43   ` Russell King
2001-02-28 20:27     ` kuznet
2001-02-27 23:01 ` Eugene Crosser
2001-02-28 20:20   ` kuznet
2001-03-19  7:37     ` Russell King
2001-03-19 18:56       ` kuznet
2001-03-21 21:54         ` Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200102271648.f1RGmLr08116@brick.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=anton@linuxcare.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.