Grep without having it show its own process in the results

ps aux | grep "[s]ome_text"
The trick here is to use the brackets [ ] around any one of the characters of the grep string. This uses the fact that [?] is a character class of one letter and will be removed when parsed by the shell. This is useful when you want to parse the output of grep or use the return value in an if-statement without having its own process causing it to erroneously return TRUE.
Sample Output
$ ps aux | grep "crond"
root      2638  0.0  0.0   1912   640 ?        S     2008   0:10 /usr/sbin/crond -l10
siegex    6312  0.0  0.0   2084   636 pts/0    R+   19:42   0:00 grep crond

$ ps aux | grep "[c]rond"
root      2638  0.0  0.0   1912   640 ?        S     2008   0:10 /usr/sbin/crond -l10

By: SiegeX
2009-02-17 02:10:50

What Others Think

This was already added
leper421 · 696 weeks and 4 days ago
Say you'll see me again private investigator indianapolis
tillyracker · 52 weeks and 4 days ago
seofox · 31 weeks 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: