From owner-freebsd-current  Tue Aug  6  9:42:44 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 295BD37B401
	for <freebsd-current@FreeBSD.ORG>; Tue,  6 Aug 2002 09:42:42 -0700 (PDT)
Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AB90443E75
	for <freebsd-current@FreeBSD.ORG>; Tue,  6 Aug 2002 09:42:40 -0700 (PDT)
	(envelope-from ache@pobrecita.freebsd.ru)
Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1])
	by nagual.pp.ru (8.12.5/8.12.5) with ESMTP id g76GgVY9001723;
	Tue, 6 Aug 2002 20:42:34 +0400 (MSD)
	(envelope-from ache@pobrecita.freebsd.ru)
Received: (from ache@localhost)
	by pobrecita.freebsd.ru (8.12.5/8.12.5/Submit) id g76GgStp001722;
	Tue, 6 Aug 2002 20:42:29 +0400 (MSD)
	(envelope-from ache)
Date: Tue, 6 Aug 2002 20:42:26 +0400
From: "Andrey A. Chernov" <ache@nagual.pp.ru>
To: Christian Weisgerber <naddy@mips.inka.de>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Signals/jobs weirdness?
Message-ID: <20020806164224.GA1606@nagual.pp.ru>
References: <aiok3e$n0h$1@kemoauc.mips.inka.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aiok3e$n0h$1@kemoauc.mips.inka.de>
User-Agent: Mutt/1.5.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On Tue, Aug 06, 2002 at 13:48:30 +0000, Christian Weisgerber wrote:
> Something is fishy with signals/jobs.  Getting suspended jobs back
> into the foreground doesn't quite work.  I don't have a clear picture
> yet of what's wrong.
> 
> -CURRENT/alpha as of August 3.  Could be a system problem, could
> be something in the new 2.05b release of bash.
> 
> Has anybody else noticed strange ^Z/fg behavior?

Yes. Read -current thread about 'su' - there is either "suspend/fg" not 
works or "stop $$/fg" not works. I "fix" it (as workaround) so suspend/fg
works as commonly needed (but not "stop $$/fg").

-- 
Andrey A. Chernov
http://ache.pp.ru/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message