X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Blake Subject: Re: xargs gives grep/gawk too much Date: Fri, 8 Dec 2006 20:53:12 +0000 (UTC) Lines: 23 Message-ID: References: <31DDB7BE4BF41D4888D41709C476B65704169472 AT NIHCESMLBX5 DOT nih DOT gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Buchbinder, Barry (NIH/NIAID) [E] niaid.nih.gov> writes: > > I get the following error message: > xargs: grep: Argument list too long > I've also gotten an equivalent error from xargs/gawk. It looks like you are picking up the cygwin version of grep/gawk, so I'm not sure why you are getting a failure. I might expect problems if it were a windows-native app, where you have a 32k limit on the args and on the environment (but ISTR the limit is distinct between the two; ie. you can pass up to 64 k of info to a Windows process). The xargs --show-limits looks like xargs added instead of subtracted, resulting in a buffer size bigger than 32k, but that may be okay if it then subtracts the space for the environment later on, so I'll have to investigate that. Can you get things to work with -s? How much data are you trying to process, anyway ('echo path/* | wc')? -- Eric Blake volunteer cygwin findutils maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/