From owner-freebsd-ports  Sun Apr 14 18:39:13 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA02090
          for ports-outgoing; Sun, 14 Apr 1996 18:39:13 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA02075
          for <ports@freebsd.org>; Sun, 14 Apr 1996 18:39:10 -0700 (PDT)
Received: (from jkh@localhost) by time.cdrom.com (8.7.5/8.6.9) id SAA16211 for ports@freebsd.org; Sun, 14 Apr 1996 18:38:25 -0700 (PDT)
Date: Sun, 14 Apr 1996 18:38:25 -0700 (PDT)
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Message-Id: <199604150138.SAA16211@time.cdrom.com>
To: ports@freebsd.org
Subject: Interesting bash bug - anyone else see this?
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.

					Jordan