From owner-freebsd-current Tue Apr 24 10: 5:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 048FF37B423 for ; Tue, 24 Apr 2001 10:05:26 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id TAA94529; Tue, 24 Apr 2001 19:05:24 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Tue, 24 Apr 2001 19:05:24 +0200 (CEST) Message-Id: <200104241705.TAA94529@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) In-Reply-To: <200104232202.f3NM25607648@hak.lan.Awfulhak.org> X-Newsgroups: list.freebsd-current User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: >> If I'm not mistaken, the size of the environment is already >> taken into account by the xargs utility (subtracted from >> ARG_MAX). So this isn't an issue at all. > > Unless xargs runs a command with lots of arguments and that command > increases the environment size then tries to run another command with > the same arguments - bang (E2BIG). True, but that's certainly not xarg's fault (and it cannot be fixed in the scope of xargs). xargs has no way to know if the command will enlarge its environment, and by what amount. In such a case it's probably up to the script writer to chose a sensible value for xargs -s . Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message