Date: Wed, 7 Aug 2002 19:12:36 +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: <20020807190540.K4931-100000@gamplex.bde.org> In-Reply-To: <20020807053012.GA3174@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 7 Aug 2002, Andrey A. Chernov wrote: > 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. It seemed to fix it for me. Maybe I have fixed kern_sig.c without noticing (I have 1091 lines of patches for it, mostly for style bugs). > 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. I had it backed out already to test this. I use an old version of bash-1 for the shell in most cases including all cases tested. 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?20020807190540.K4931-100000>