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.


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.

Universal configuration monitoring and system of record for IT.
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

May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!
Hide

Top Tags

Hide

Functions

Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Easily search running processes (alias).

Terminal - Easily search running processes (alias).
alias 'ps?'='ps ax | grep '
2009-02-05 13:36:37
User: fzero
Functions: alias grep
55
Easily search running processes (alias).

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Interesting to find something so simple that I also created. Only difference is I used psax for the command, but yours is easier to type and makes more sense. Thanks. :)

Comment by pkkid 394 weeks and 4 days ago

Why not:

pgrep
Comment by porges 394 weeks and 4 days ago

@porges

It's just a matter of taste, really. I'm into ruby so I like asking things. :-)

Comment by fzero 394 weeks and 3 days ago

I add in a few w's in case the command is too long and make sure grep is case insensitive

alias psg='ps axwww | grep -i'

Then you can search for something like the finder (Finder.app) like this.

psg finder

59457 ?? S 2:35.56 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder -psn_0_12430298

Comment by claytron 393 weeks and 2 days ago

@porges

"pgrep" only displays the PIDs. "pgrep -l" only displays the PID and process name. "ps aux" displays more info.

Comment by leper421 393 weeks and 2 days ago

A bash function version

psg() { ps auxw | grep -i $1 | grep -v grep; }
Comment by starchox 392 weeks and 6 days ago

Refined bash function version, omit use another grep, using square bracket trick

psg() { ps auxw | grep -i $(echo $1 | sed "s/^\(.\)/[\1]/g"); }

Comment by starchox 392 weeks and 6 days ago

A very similar thing I've been using for years:

pu() { ps auxw | egrep "$1|PID" | grep -v egrep; }

It retains the ps header line.

Comment by hypatiafu 392 weeks and 5 days ago
pgrep -lf syslog

4855 /sbin/syslogd -u syslog

Comment by alexfoo 391 weeks and 4 days ago

I've used:

p() { ps auxw | grep -i $1 | grep -v grep; }

For years and yes, I know the double grep is inefficient. Is the sed solution really worth it though?

Comment by ajt 387 weeks and 6 days ago

The sed trick is more specific. With the double grep you risk matching other greps, processes with the substring 'grep' in its name/args, etc.

On the efficiency side, both need an additional fork. The square bracket trick can be done in shell.

psg () { ps auxw | grep \[${1:0:1}\]${1:1} ; }
Comment by funollet 384 weeks and 6 days ago

psg() { ps auxw | grep -i '[ ]\?'"$1"; }

(Having fun with backslashes and quotes...)

Comment by myname 371 weeks and 5 days ago

Your point of view

You must be signed in to comment.