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

Find the process you are looking for minus the grepped one

Terminal - Find the process you are looking for minus the grepped one
psg() { ps aux | grep "[${1[1]}]${1[2,-1]}"; }
2009-09-07 04:37:11
User: jedahan
Functions: grep ps
-5
Find the process you are looking for minus the grepped one

alias ps?='psg' for maximum hawtness. Works in bash or zsh.

Alternatives

There are 2 alternatives - 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.

ps axu | grep [a]pache2
2012-12-15 19:37:19
User: EBAH
Functions: grep ps
12

Trick to avoid the form:

grep process | grep - v grep

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)

Know a better way?

If you can do better, submit your command here.

What others think

pgrep processname

part of the 'procps' package at least under debian/ubuntu. Once installed, works in any shell :-).

Comment by bwoodacre 271 weeks and 5 days ago

That only returns pids though.

Comment by DaveQB 271 weeks and 5 days ago

if you invoke pgrep with -l then you get the process name, but then chances are you just want

ps aux | grep [p]rocessname

which was already posted on commandlinefu.

Comment by bwoodacre 271 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts