Date: Wed, 10 Aug 2011 21:51:32 -0500 From: Adam Vande More <amvandemore@gmail.com> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: Raimund Steger <rs@mytum.de>, freebsd-stable@freebsd.org Subject: Re: Recent STABLE unable to start process in background Message-ID: <CA%2BtpaK3bwFygV8Q2CuW5=YLp_qc53aUyJBbzzqajLpXx-rdLhQ@mail.gmail.com> In-Reply-To: <20110811012207.GA86377@icarus.home.lan> References: <CA%2BtpaK1Gv4nPVxAqi0pWOBJSKpOpBV1ExDKPrW7KCburmS7C1w@mail.gmail.com> <4E431C3A.6080707@mytum.de> <20110811012207.GA86377@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 10, 2011 at 8:22 PM, Jeremy Chadwick <freebsd@jdc.parodius.com>wrote: > > Looks like SIGTTOU (output from background process)? > > This should be controllable with stty -tostop. > > (But why has it changed...?) > > On all our RELENG_8 systems (though I use bash), -tostop is default. > Hm, it seems there might be something wrong with zsh. stty -a on an old and new setup produces identical output with -tostop set. The old setup runs zsh-4.3.10_3 which works correctly, but zsh-4.3.12 doesn't work on the new. The latest bash works fine on the new. I can file a bug report on zsh, but could someone confirm that it's the likely candidate for a problem so I don't send anyone on a wild goose chase? Thanks, -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK3bwFygV8Q2CuW5=YLp_qc53aUyJBbzzqajLpXx-rdLhQ>