Kill all processes belonging to a user

ps wwwwuax|awk '/command/ { printf("kill -9 %s\n",$2) }'|/bin/sh
Okay, commands like this are a bit of a personal peeve. awk(1) operates on a /pattern/ {action} paradigm and yet I see people leave out the /pattern/ portion of an awk command all the time, opting to use grep or sed instead. You'll save yourself some typing and time if you include the /pattern/ with your {action}.

By: jetdillo
2012-08-14 21:44:38

4 Alternatives + Submit Alt

What Others Think

Not bad, but you can save a few characters by changing printf to print: ps wwwwuax|awk '/command/ { print "kill -9 "$2 }'|/bin/sh Then another few by using a subshell execution rather than the pipe: kill -9 $(ps wwwwuax|awk '/command/ { print $2 }') This works, but it exposes a bug in the original command. Awk's pattern matches awk itself. In the original command the error message is lost.
flatcap · 427 weeks and 6 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands

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.


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: