X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 29 Feb 2008 14:42:49 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: another minor cygcheck "nit" Message-ID: <20080229194249.GB14180@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <47C79C75.5000508@tlinx.org> <20080229092105.GP9539@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080229092105.GP9539@calimero.vinschen.de> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Fri, Feb 29, 2008 at 10:21:05AM +0100, Corinna Vinschen wrote: >On Feb 28 21:47, Linda Walsh wrote: >> cygcheck doesn't handle the "max arg length" as shown by "xargs"... >> I.e. - >> >>> cygcheck -f /bin/* >> bash: /usr/bin/cygcheck: Argument list too long >>> echo /bin/*|xargs cygcheck -f >> xargs: cygcheck: Argument list too long >> >> #Note: >> cygcheck /bin/[a-r]* # works (wc -wc = 1780 32365) >> cygcheck /bin/[a-s]* # fails (wc -wc = 1874 33917) >> >> # -- looks like a 2^15 boundary prob? >> >>> xargs --show-limits >> Your environment variables take up 3867 bytes >> POSIX upper limit on argument length (this system): 1042661 >> POSIX smallest allowable upper limit on argument length (all systems): 4096 >> Maximum length of command we could actually use: 1038794 >> Size of command buffer we are actually using: 1042661 >> >> Guess cygcheck isn't a POSIX app? > >cygcheck is a native app. For hopefully obvious reasons... cgf -- 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/