This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: xargs gives grep/gawk too much


On Wed, Dec 13, 2006 at 02:17:56PM -0500, Buchbinder, Barry (NIH/NIAID) [E] wrote:
>Christopher Faylor wrote on Sunday, December 10, 2006 1:34 AM:
>>On Sun, Dec 10, 2006 at 01:21:19AM -0500, Christopher Faylor wrote:
>>>On Sat, Dec 09, 2006 at 11:31:05AM -0800, Karr, David wrote:
>>>>If the point of this note is to get your pipeline to work, would it
>>>>help if you added something like "-n 30" to the xargs command?  This
>>>>should execute one instance of 'grep -l -e "error '1234567890'"' for
>>>>every 30 lines of output from the previous pipe entry.
>>>>
>>>>$ echo path/* | \ tr ' ' '\n' | \ grep -v -e '\*' | \ xargs -r grep -l
>>>>-e "error '1234567890'" | \ rest_of_pipe
>>>
>>>I'm sure that the point of the note was to report a Cygwin bug.
>>
>>...but I can't duplicate this with the latest snapshot...

I wasn't paying close attention to this thread but just in case there
was some misinformation here: you have to mount the directory with -X in
order to reap the benefit of cygwin's argument handling.  Otherwise, you
are limited to <32K command line sizes.

And, as I said, I could't duplicate Eric's problem with the current
snapshot.

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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]