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 pids without specific pid

Terminal - kill some pids without specific pid
kill -9 `ps aux | grep "search_criteria" | awk '{if ($2 != pid) print $2}'`
2010-09-16 08:52:59
User: ozgurkuru
Functions: awk grep kill
-6
Up
Down
kill some pids without specific pid

search_criteria = what do you want to kill

pid = pid of you dont kill

Add to favourites | Report as malicious

Alternatives

There are 3 alternatives - vote for the best!

Terminal - Alternatives
pkill -9 search_criteria
2010-09-16 10:02:25
User: hadace
4
Up
Down
kill some pids without specific pid

pgrep, pkill - look up or signal processes based on name and other attributes

Comments (2) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

pkill -9 search_criteria not same with my command.

my command kill some jobs in same job groups. for example,

you have this scripts,

/var/scripts/backup_A.py

/var/scripts/backup_B.py

/var/scripts/backup_C.py

And you run all of this scripts. And you want to kill backup_A.py and backup_C.py

so

you put backup_B.py's pid to this command... such us:

kill -9 `ps aux | grep "var/scripts" | awk '{if ($2 != backup_B.py's_pid) print $2}'`

Comment by ozgurkuru 140 weeks and 2 days ago

Of course it's overcomplicated and in most cases pgrep or killall is what you need. BTW grep is not needed here, awk can do its job

kill -9 `ps aux | awk '/search_criteria/{if ($2 != pid) print $2}'`

Comment by zolden 140 weeks and 2 days ago

@zolden thanks for update.

Comment by ozgurkuru 140 weeks and 2 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts