Date: Wed, 25 Jun 2003 19:20:01 +1000 From: "Tim J. Robbins" <tjr@freebsd.org> To: Juli Mallett <jmallett@freebsd.org>, freebsd-current@freebsd.org, Andrey Chernov <ache@nagual.pp.ru> Subject: Re: tcsh being dodgy, or pipe code ishoos? Message-ID: <20030625192001.A10405@dilbert.robbins.dropbear.id.au> In-Reply-To: <20030625074151.GY57612@funkthat.com>; from gurney_j@efn.org on Wed, Jun 25, 2003 at 12:41:51AM -0700 References: <20030624183515.A42570@FreeBSD.org> <1056499632.662.7.camel@timon.nist> <3EF922BE.4070803@acm.org> <20030624234707.A59666@FreeBSD.org> <20030625001525.A60867@FreeBSD.org> <20030625060450.GX57612@funkthat.com> <20030625074151.GY57612@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 25, 2003 at 12:41:51AM -0700, John-Mark Gurney wrote: [...] > So, now the question is, do we fix xargs to deal with unexpected > children? Or fix the shells in question? (tcsh and zsh seem to suffer > this problem) > > To me, fixing xargs is correct since it prevents another possible > future abusers of this "feature". Feel free to get rid of the -P option. What tcsh and zsh are doing is a fairly bad idea though, and it will break more than just xargs. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030625192001.A10405>