From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-request@euclid.skiles.gatech.edu>
Received: (qmail 12812 invoked from network); 26 Dec 1996 00:36:36 -0000
Received: from euclid.skiles.gatech.edu (list@130.207.146.50)
  by coral.primenet.com.au with SMTP; 26 Dec 1996 00:36:36 -0000
Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id TAA14353; Wed, 25 Dec 1996 19:36:30 -0500 (EST)
Resent-Date: Wed, 25 Dec 1996 19:32:30 -0500 (EST)
Date: Thu, 26 Dec 1996 01:33:23 +0100 (MET)
From: Wolfgang Hukriede <whukriede@ifm.uni-kiel.de>
Message-Id: <199612260033.BAA26825@sally.ifm.uni-kiel.de>
To: zsh-users@math.gatech.edu
Subject: piped rsh hangs on nextstep
Resent-Message-ID: <"_KFnY3.0.GV3.TUSmo"@euclid>
Resent-From: zsh-users@math.gatech.edu
X-Mailing-List: <zsh-users@math.gatech.edu> archive/latest/563
X-Loop: zsh-users@math.gatech.edu
X-Loop: zsh-workers@math.gatech.edu
Precedence: list
Resent-Sender: zsh-workers-request@math.gatech.edu

On Nextstep3.2 commands similar to:

        zsh-3.0.2> rsh remotehost cat somefile | wc

hang. After ^C is hit, the shell prints:

        [1]    suspended (tty input)  rsh remotehost cat somefile |
               interrupt              wc

This only happens when the rsh-output is piped into the local command.

        zsh-3.0.2> rsh remotehost cat somefile </dev/null | wc
        zsh-3.0.2> rsh -n remotehost cat somefile | wc
        zsh-3.0.2> rsh remotehost cat somefile

are ok. Also unsetopt monitor helps.

I checked the same with zsh-3.0.2 on Linux-2.0 and Osf3.2, there are no
such problems on both of them, even when remotehost is the Next.

What now? Enable RSH_BUG_WORKAROUND? But that's for the other side, as
I understand it??

Clueless, Wolfgang.   (Hints appreciated.)