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.
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:
Kill all process that concide whit PATTERN
A pretty nice display of processes.
Tested in bash on AIX & Linux, used for WAS versions 6.0 & up. Sorts by node name.
Useful when you have vertically-stacked instances of WAS/Portal. Cuts out all the classpath/optional parameter clutter that makes a simple "ps -ef | grep java" so difficult to sort through.
Gets the current system user running a process with the specified pid
Same as previous but compatible with BSD/IPSO
(separator = $IFS)
This command will allow to search for duplicate processes and sort them by their run count. Note that if there are same processes run by different users you'll see only one user in the result line, so you'll need to do:
ps aux | grep <process>
to see all users that run this command.
Find the USERid of a SUDOed user who has either left their terminal logged in or for scripting purposes to track who ran what commands.
This only applys to users that do sudo su - USERNAME. not sudo su USERNAME
Sudo su without the dash allows use of (echo $SUDO_USER)
to be executed from root. this works well on most commercial unix systems, have not tried on linux systems.
Use ps instead of top. But do not use BSD options at all, they are confusing.
Use "s=" or "state=" to show consice process statuses.
Let's supose some moron used some m$ shit to commit to a later svnsynced repo. On a svn sync all his message logs cause a svnsync: Error setting property 'log': this commands finds all its contributions and fix all his commit logs
Outputs the PID of any given file run from a command line... Hope it helps!
This one-liner will use strace to attach to all of the currently running apache processes output and piped from the initial "ps auxw" command into some awk.
I know you can use pidof but with this you can know the specific PID with his command arguments (useful if you're running various proccess with same application)
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.
Look mah! All pipes