From owner-freebsd-ports  Tue Apr 16 02:11:48 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA27446
          for ports-outgoing; Tue, 16 Apr 1996 02:11:48 -0700 (PDT)
Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA27427
          for <ports@freebsd.org>; Tue, 16 Apr 1996 02:11:22 -0700 (PDT)
Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id LAA29444 for ports@freebsd.org; Tue, 16 Apr 1996 11:12:19 +0200
Message-Id: <199604160912.LAA29444@nixpbe.pdb.sni.de>
Subject: Re: Interesting bash bug - anyone else see this?
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Tue, 16 Apr 96 11:11:09 MDT
From: Greg Lehey <lehey.pad@sni.de>
Cc: ports@freebsd.org
In-Reply-To: <199604150138.SAA16211@time.cdrom.com>; from "Jordan K. Hubbard" at Apr 14, 96 6:38 pm
X-Mailer: xmail 2.4 (based on ELM 2.2 PL16)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>
> I just noticed it, myself.  It doesn't happen in sh or csh, so it's
> definitely one for -bash and -current (if not also -stable; I dunno!).
>
> <go to a directory with many files in it>
> root@reason-> ls -lt | more
> ^Z
> [2]+  Done                    ls -lt | more
> root@reason-> fg
> ls -lt | more
> Broken pipe
>
> Bug #1: Upon suspending, bash erroneously reports the background job's status
> 	as "Done", not "Suspended"
>
> Bug #2: Upon resuming, we're hosed - the pipe breaks.
>
> Note that this does NOT occur once ls actually starts filling the pipe,
> then you can background and foreground it all day long and nothing bad
> happens.

FWIW, I've tried this on an SNI box (System V.4, R4400).  It does much
the same thing, except that it needs a ^C to get a prompt after the
^Z.  Looks like it isn't a FreeBSD problem.

Greg