Date: Wed, 7 Aug 2002 09:30:12 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Bruce Evans <bde@zeta.org.au> Cc: Christian Weisgerber <naddy@mips.inka.de>, freebsd-current@FreeBSD.ORG Subject: Re: Signals/jobs weirdness? Message-ID: <20020807053012.GA3174@nagual.pp.ru> In-Reply-To: <20020807045914.P2924-100000@gamplex.bde.org> References: <20020806164224.GA1606@nagual.pp.ru> <20020807045914.P2924-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 07, 2002 at 05:00:21 +1000, Bruce Evans wrote: > > > > 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. kernel_sig.c change not fix this bug. If su fix will be backed out, situation triggered: "suspend/fg" will not works, but "stop $$/fg" start works. Just check it with very recent -current: when this change is backed out, "suspend/fg" kills login shell (even with multiply su levels). So, kernel bug still present, and I see no activity in fixing direction. -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020807053012.GA3174>