From owner-freebsd-current@FreeBSD.ORG Wed Jun 25 03:06:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A7BC37B401; Wed, 25 Jun 2003 03:06:38 -0700 (PDT) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A00643F3F; Wed, 25 Jun 2003 03:06:37 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc0fm.dialup.mindspring.com ([209.86.1.246] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19V7Ah-0004a3-00; Wed, 25 Jun 2003 03:06:36 -0700 Message-ID: <3EF973CB.594401B7@mindspring.com> Date: Wed, 25 Jun 2003 03:04:59 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John-Mark Gurney References: <20030624183515.A42570@FreeBSD.org> <1056499632.662.7.camel@timon.nist> <3EF922BE.4070803@acm.org> <20030625001525.A60867@FreeBSD.org> <20030625074151.GY57612@funkthat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40fdd522f5a7183f5d53f5f914fad2daca8438e0f32a48e08350badd9bab72f9c350badd9bab72f9c cc: Juli Mallett cc: Andrey Chernov cc: freebsd-current@freebsd.org cc: "Tim J. Robbins" Subject: Re: tcsh being dodgy, or pipe code ishoos? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2003 10:06:39 -0000 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". Fixing the shells is correct, since it means they don't break on the next program like xargs (e.g. have you tried "team", etc. to see if they break too? Even if "team" specifically doesn't, there's no guarantee something else won't...). -- Terry