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:
(1) don't run twice, or the same folder will occur in $PATH.
(2) otherwise you need to start a new terminal
a pretty simple script when running java programs from command line
a simple interactive tool to convert Simplified Chinese (typed by pinyin) to Traditional Chinese
-n is very important, otherwise it's string comparison
Pros: the format is very simple, there is no need to show every columns, and full command with args
the first column is memory consumption %
the second column is pid
the third is just the command (without full arguments, most application's arguments are too long)
You can decide which application to kill then.
parrallel execution of a command on remote host by ssh or rsh or ...
very useful for cluster management (software update)
This is usefull when we don't know the exact name of the process, but the application name
A limitation is that the regular expression only tries to match the last part of the full command (i.e. the bin file name itself).
But this is way shorter than the following one:
ps axww | grep SomeCommand | awk '{ print $1 }' | xargs kill