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/
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.
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
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:
There are 3 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
Perhaps a use of killall instead?
or pkill?
and please don't use kill -9, this is very bad behaviour. Please try it with kill -15 and if it doesn't end the process kill -2. Then you can still use kill -9.
Wow. grep piped to grep piped to awk. Never thought I'd see that.
Apart from the fact that there's pkill and killall (depending on the OS), there are quite a lot of things that can be improved in this command line.
First, this is a nice trick to avoid the ugly "grep -v grep" part:
ps ax | grep '[p]rocessname'Note that the first letter is enclosed in square brackets. This regular expression will match 'processname', but it will not match the grep command itself.
Second, it doesn't make sense to pipe from grep to awk because awk has a "built-in grep":
ps ax | awk '/[p]rocessname/{print $1}'