Date: Wed, 7 Aug 2002 01:10:04 +1000 From: Tim Robbins <tjr@FreeBSD.ORG> To: Christian Weisgerber <naddy@mips.inka.de> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Signals/jobs weirdness? Message-ID: <20020807011004.A9927@dilbert.robbins.dropbear.id.au> In-Reply-To: <aiok3e$n0h$1@kemoauc.mips.inka.de>; from naddy@mips.inka.de on Tue, Aug 06, 2002 at 01:48:30PM %2B0000 References: <aiok3e$n0h$1@kemoauc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 06, 2002 at 01:48:30PM +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. Specifically, suspending then fg'ing chpass, chfn, chsh and su does not work correctly. It seems to be bringing the wrong process to the foreground the first time I try 'fg', then the second time around it works. This was -CURRENT on i386, probably about the 20th of July, using sh, tcsh, and pdksh. I believe it was fine in early July; ref5 is running a kernel from July 1 and it works properly. Tim 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?20020807011004.A9927>