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).

Commands using ps from sorted by
Terminal - Commands using ps - 204 results
ps axu | awk '{if (NR <=7) print; else if ($8 == "D") {print; count++} } END {print "Total status D: "count}'
2011-03-21 04:32:56
User: eneko
Functions: awk ps
0
Up
Down
count processes with status
Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -C apache o pid= | sed 's/^/-p /' | xargs strace
2011-03-15 08:46:33
User: depesz
Functions: ps sed xargs
Tags: awk token ps strace tokenizer
-1
Up
Down
easily strace all your apache processes
Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps auxw | grep sbin/apache | awk '{print"-p " $2}' | xargs strace
2011-03-14 21:45:22
User: px
Functions: awk grep ps xargs
Tags: awk token ps tokenizer
4
Up
Down
easily strace all your apache processes

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.

Show sample output | Comments (7) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
pss() { ps -eo pid,args | sed '/'"$1"'/!d;/sed/d' ; }
2011-03-14 15:51:49
User: vando
Functions: ps sed
-2
Up
Down
Find the correct PID

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)

Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -eo pmem,pid,comm --no-headers | sort -k1 -rn | head -10
2011-03-11 04:51:35
User: dexterhu
Functions: head ps sort
0
Up
Down
show top 10 most memory hungry process with a simple format of (%mem, pid, short command)

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.

Show sample output | Comments (2) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps ax | egrep "*.exe|*exe]" | awk '{ print $1 }' | xargs kill
2011-03-01 09:48:47
User: coffeeaddict_nl
Functions: awk egrep ps xargs
Tags: kill wine exe
1
Up
Down
kill all running instances of wine and programs runned by it (exe)

Look mah! All pipes

Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps ax > processes && cat processes | egrep "*.exe |*exe]" | awk '{ print $1 }' > pstokill && kill $(cat pstokill) && rm processes && rm pstokill
2011-02-26 16:13:58
User: sxiii
Functions: awk cat egrep kill ps rm
Tags: kill wine exe
-4
Up
Down
kill all running instances of wine and programs runned by it (exe)

This command kills all wine instances and each EXE application working on a PC.

Here is command info:

1) ps ax > processes = save process list to file named "processes" (we save it because we don't wont egrep to be found in the future)

2) cat processes | egrep "*.exe |*exe]" = shows the file "processes" and after greps for each *.exe and *exe] in it

3) | awk '{ print $1 }' > pstokill = saves processes PID's to file "pstokill" using awk filter

4) kill $(cat pstokill) = kills each PID in file pstokill, which is shown by cat program

5) rm processes && rm pstokill = removes temporary files

Show sample output | Comments (2) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -p $$
2011-02-05 16:22:17
User: psykotron
Functions: ps
3
Up
Down
Figure out what shell you're running

short, sweet, and works after sudoing a new shell.

Show sample output | Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -o comm= -p $$
2011-02-05 11:54:42
User: depesz
Functions: ps
0
Up
Down
Figure out what shell you're running

First version was "ps uw -p $$", but current "ps -o comm= -p $$" just gives shell name

Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps ho command $$
2011-02-05 10:24:33
User: j_melis
Functions: command ps
-3
Up
Down
Figure out what shell you're running
Comments (3) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -ef | grep c\\ommand
2011-01-04 11:43:14
User: ioggstream
Functions: grep ps
Tags: grep ps
6
Up
Down
Find the process you are looking for minus the grepped one

faster ;) but your idea is really cool

Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -o user,%cpu,%mem,command
2010-12-08 10:35:25
User: unixmonkey4200
Functions: ps
Tags: ps
0
Up
Down
'micro' ps aux (by mem/cpu)

Using ps options rather than filtering.

Show sample output | Comments (1) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps aux | awk '{print($1" "$3" "$4" "$11);}' | grep -v "0.0"
2010-12-08 09:59:39
User: cas_alexi
Functions: awk grep ps
1
Up
Down
'micro' ps aux (by mem/cpu)

mac os x:

ps aux | awk '{print($1" "$3" "$4" "$11);}' | grep -v "0,0"

linux:

ps aux | awk '{print($1" "$3" "$4" "$11);}' | grep -v "0.0"

Show sample output | Comments (1) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -eo %cpu,args | grep -m1 PROCESS | awk '{print $1}'
2010-11-30 08:15:08
User: lin72
Functions: awk grep ps
1
Up
Down
print a cpu of a process
Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -eo args,%cpu | grep -m1 PROCESS | tr 'a-z-' ' ' | awk '{print $1}'
2010-11-29 17:43:52
User: lin72
Functions: awk grep ps tr
-1
Up
Down
print a cpu of a process
Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -o etime `pidof firefox` |grep -v ELAPSED | sed 's/\s*//g' | sed "s/\(.*\)-\(.*\):\(.*\):\(.*\)/\1d \2h/; s/\(.*\):\(.*\):\(.*\)/\1h \2m/;s/\(.*\):\(.*\)/\1m \2s/"
2010-11-28 03:27:24
User: jsymonkj
Functions: grep ps sed
3
Up
Down
To find the uptime of each process-id of particular service or process
Comments (2) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -o pid,lwp,lstart --pid 797 -L
2010-11-24 17:04:08
User: jkharness87
Functions: ps
1
Up
Down
List Threads by Pid along with Thread Start Time

This command will list all threads started by a particular pid along with the start time of each thread. This is very valuable when diagnosing thread leaks.

Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -eorss,args | sort -nr | pr -TW$COLUMNS | head
2010-11-24 04:17:54
User: cogsmos
Functions: pr ps sort
2
Up
Down
Top ten memory hogs

Inspired by #7065

Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -o euid,egid --ppid `netstat --inet --inet6 -pln|awk '/:80 / { split($7,tmp, "/"); print tmp[1]; }'`|sort |uniq|grep -v EUID
2010-11-18 21:22:29
User: chx
Functions: awk grep ps sort
-1
Up
Down
Find the uid and gid of your apache process

This command allows you to find the effective uid and gid of the Apache process regardless of process name (which can be apache2 or httpd depending on distro).

Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -e -orss=,args= | sort -b -k1,1n | pr -TW$COLUMNS
2010-11-17 14:55:16
User: lxneng
Functions: pr ps sort
1
Up
Down
memory usage
Comments (1) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps ax -L -o pid,tid,psr,pcpu,args | sort -nr -k4| head -15 | cut -c 1-90
2010-11-17 01:04:31
User: strzel_a
Functions: cut head ps sort
1
Up
Down
Show CPU usage for EACH cores
Comments (2) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps uw --ppid $PID
2010-11-13 22:21:09
User: depesz
Functions: ps
1
Up
Down
Given $PID, print all child processes on stdout

Simpler.

Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps axo pid,ppid | awk "{ if ( \$2 == $PID ) { print \$1 }}")
2010-11-13 19:41:28
User: daniele
Functions: awk ps
0
Up
Down
Given $PID, print all child processes on stdout
Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
set $(ps -e o command= | grep "^/usr/bin/X "); while [ x"$1" != x"-auth" ]; do shift; done; sudo x11vnc -display :0 -auth "$2"
2010-11-05 14:51:24
User: bandie91
Functions: grep ps set sudo
Tags: x11vnc gdm
1
Up
Down
start a vnc server session to connect to a gdm login screen
Comments (0) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate
ps -u $USER -lf | grep -vE "\-bash|sshd|ps|grep|PPID" > .tmpkill; if (( $(cat .tmpkill | wc -l) > 0 )); then echo "# KILL EM ALL"; cat .tmpkill; cat .tmpkill | awk '{print $4}' | xargs kill -9; else echo "# NOTHING TO KILL"; fi; cat .tmpkill; rm .tmpkill;
2010-11-04 04:16:50
User: zsugiart
Functions: awk cat echo grep kill ps rm wc xargs
0
Up
Down
kill all process that belongs to you

Kills all process that belongs to the user that runs it - excluding bash, sshd (so putty/ssh session will be spared). The bit that says grep -vE "..." can be extended to include ps line patterns that you want to spare.

If no process can be found on the hitlist, it will print # NOTHING TO KILL. Otherwise, it will print # KILL EM ALL, with the cull list.

Comments (1) | Add to favourites | Report as malicious | Submit alternative | Report as a duplicate