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.

OpenID
or
Sign in Register

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

Hide

Credits

Site by David Winterbottom (user root).

kill some process (same as others) but parsing to a variable

Terminal - kill some process (same as others) but parsing to a variable
pkill -9 -f program
2009-07-12 14:46:14
User: ioggstream
1
Up
Down
kill some process (same as others) but parsing to a variable

Kills a process matching program. I suggest using

$ pgrep -fl program

to avoid over-killings

Nice the following: kills all bash process owned by guest

$ pkill -9 -f bash -u guest

Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
ps -ef | grep PROCESS | grep -v grep | awk '{print $2}' | xargs kill -9
2009-02-21 15:55:38
User: f4nt
Functions: awk grep kill ps xargs
1
Up
Down
ps -ef | grep PROCESS | grep -v grep | awk '{print $2}' | xargs kill -9

kills all pids matching the search term of "PROCESS". Be careful what you wish for :)

Comments (6) | Add to favourites | Report as malicious
tokill=`ps -fea|grep process|awk '{ printf $2" "}'`; kill -9 $tokill;
2009-07-11 01:40:29
User: jhansen
Functions: awk grep kill printf
-3
Up
Down
kill some process (same as others) but parsing to a variable
Comments (1) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

Should use -9 as signal of last resort.

Kill -15 (the default if omitted) is the correct signal to send, failing that, try -1 and then possibly -11.

Reason being is -9 does not allow the process to do proper cleanup which can leave things in an inconsistent state, potentially causing data corruption.

Comment by Mehuge 200 weeks and 3 days ago

just to tell that you can specify signals..

nice explaination anyway ;)

Comment by ioggstream 200 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts