Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.


If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

grep processes list avoiding the grep itself

Terminal - grep processes list avoiding the grep itself
ps axu | grep [a]pache2
2012-12-15 19:37:19
User: EBAH
Functions: grep ps
12
grep processes list avoiding the grep itself

Trick to avoid the form:

grep process | grep - v grep

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
ps aux | grep [p]rocess-name
2009-08-13 05:44:45
User: olorin
Functions: grep ps
62

As an alternative to using an additional grep -v grep you can use a simple regular expression in the search pattern (first letter is something out of the single letter list ;-)) to drop the grep command itself.

pgrep command_name
ps -ef | grep c\\ommand
2011-01-04 11:43:14
User: ioggstream
Functions: grep ps
Tags: grep ps
6

faster ;) but your idea is really cool

ps -C command
2009-08-14 15:30:42
User: recursiverse
Functions: ps
5

preferred way to query ps for a specific process name (not supported with all flavors of ps, but will work on just about any linux afaik)

ps -ef | awk '/process-name/ && !/awk/ {print}'
2009-08-19 11:22:09
User: dopeman
Functions: awk ps
1

This does the same thing as many of the 'grep' based alternatives but allows a more finite control over the output. For example if you only wanted the process ID you could change the command:

ps -ef | awk '/mingetty/ && !/awk/ {print $2}'

If you wanted to kill the returned PID's:

ps -ef | awk '/mingetty/ && !/awk/ {print $2}' | xargs -i kill {}

Know a better way?

If you can do better, submit your command here.

What others think

This works:

ps axu | grep apa\\che

double backslash can be anywhere within the pattern

Comment by tedkozma 97 weeks and 6 days ago

I use something like this:

auxer () { ps aux | grep -i "$(echo "$1" | sed "s/^\(.\)\(.*$\)/\[\1\]\2/")" }
Comment by redshadowhero 97 weeks and 5 days ago

Can someone please explain why this works?

Comment by Mikecron 97 weeks and 2 days ago

I found the explanation given by user "leper421" here:

http://www.commandlinefu.com/commands/view/402/exclude-grep-from-your-grepped-output-of-ps-alias-included-in-description

'This works because "[h]ttpd" matches only an "h" followed by "ttpd". The line that is printed by "ps aux" is "[h]ttpd" which includes the brackets, therefor not matching. Clever.'

Comment by Mikecron 97 weeks and 2 days ago

Can also be done with awk:

$ ps axu | awk '/[a]pache2/'

To extract a PID:

$ ps axu | awk '/[a]pache2/ {print $1}'

But wasn't pgrep written to solve this ?

pgrep -l apache2 pgrep apache2
Comment by zlemini 96 weeks ago

Hi Mikecron, sorry for late reply, this commands works because of regular expression issues.

When you use square brakets in a regexp it means: a chararcter part of this set.

Example:

[a-z]pache: match apache, bpache, cpache, ... , zpache

[a]pache: matches only apache

So when you type the command it filters all the lines containins the word "apache".

If you are able to see the process list (ps -ef) in the exact moment as grep runs you would see a line containing "grep [a]pache".

So why the grep process isn't shown?

Because regexp([a]pache) != string([a]pache)

Hope this is clear. Bye

Comment by EBAH 96 weeks ago

Dear zlemini, I admit I didn't know pgrep.

Since I work on a variety of OSes (Linux, Solaris, HP-UX) I tend to be as conservative as possible, so I prefer to use the same command on all the systems instead of variants.

One example above all: one script for all OSes instead of three is easier to maintain.

Anyway I'll have a look to the pgrep, I'm courious.

Thanks!

Comment by EBAH 96 weeks ago

Your point of view

You must be signed in to comment.

Related sites and podcasts