for too many arguments by *

echo *.log | xargs <command>
grep ERROR *.log -bash: /bin/grep: Argument list too long echo *.log | xargs grep ERROR /dev/null 20090119.00011.log:DANGEROUS ERROR

By: mikeda
2009-02-22 11:32:55

What Others Think

Sorry, but this does not solve your problem. The shell says "Argument list too long", not the grep command. The echo command will give the same error. This solves the problem: find . -type f -name \*.log -maxdepth 0 | xargs grep ERROR /dev/null
tonk · 665 weeks and 3 days ago
>> The echo command will give the same error. Please try them. echo * /bin/echo * The "echo" is a shell builtin command.
mikeda · 665 weeks and 2 days ago
seofox · 1 week and 3 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: