Date: Wed, 7 Aug 2002 05:00:21 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: "Andrey A. Chernov" <ache@nagual.pp.ru> Cc: Christian Weisgerber <naddy@mips.inka.de>, <freebsd-current@FreeBSD.ORG> Subject: Re: Signals/jobs weirdness? Message-ID: <20020807045914.P2924-100000@gamplex.bde.org> In-Reply-To: <20020806164224.GA1606@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 6 Aug 2002, Andrey A. Chernov wrote: > 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"). That's an old thread which concluded with fixing kern_sig.c but not backing out the "fix" in su.c. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020807045914.P2924-100000>