Commands using ps (300)
-
Sets the exec bit on a file. Show Sample Output
0svn ps svn:executable yes /web/itscripts/check_mail.plproperty -
This will find all the -Xmx[BIGINT] running on a system, add them up for you and give you the total. Show Sample Output
0output=$(ps -ef|grep -i java 2>/dev/null); for w in ${output[@]}; do if [[ $w =~ .*Xmx.* ]]; then result=$(grep -oP "[0-9]+" <<< $w); echo $result ;fi ; done| awk 'BEGIN {sum=0} {for(i=1; i<=NF; i++) sum+=$i } END {print sum}' -
Llist all the processes in the run queue.
0ps r -A -
Add up the amount of memory your processes are using and display the total. Replace marcanuy with your desired username. Show Sample Output
0ps -u marcanuy -o pid,rss,command | awk '{print $0}{sum+=$2} END {print "Total", sum/1024, "MB"}' -
This command will show the sum total of memory used in gigabytes by a program that spawns multiple instances of itself. Replace chrome with whatever program's memory usage you are investigating. This command is rather useless on software that only spawns a single instance of itself. Show Sample Output
0ps -eo pmem,comm | grep chrome | cut -d " " -f 2 | paste -sd+ | bc -
0while [ 1 ] ;do ps aux|awk '{if ($8 ~ "D") print }'; sleep 1 ;done
-
Run one script after another in such a way that second script starts after finishing first one. Without using Pipe | or ampercent && i.e. the first process is already running and you want second one to start after the first one finishes. And this can be done in different folder in case the output of second script will affect the output of first script. So run this on any folder you wish to. Where $PID is the process id of the already running job (add PID number) script2 is your script you wish to run after first script ends sleep 1 is sleep for one second (SUFFIX may be ?s? for seconds (the default), ?m? for minutes, ?h? for hours or ?d? for days, read man sleep) Show Sample Output
0while ps -p $PID; do sleep 1; done; script2 -
Displays memory usage for individual instances of an application that spawns multiple instances of itself. This command also works on single process applications. Show Sample Output
0ps -eo pmem,comm | grep application-name -
0ps -efa | grep httpd | grep -v grep | awk '{ print $2 }' |xargs
-
0ps aux | grep 'httpd' | awk '{print $6/1024 " MB";}'
-
0ps aux | grep 'httpd' | awk '{print $6/1024;}' | awk '{avg += ($1 - avg) / NR;} END {print avg " MB";}'
-
0ps aux | grep 'mysql' | awk '{print $6/1024 " MB";}'
-
There are times when a X Window server hangs. When this happens, you can log in on a terminal and kill the Xorg process (i.e. the X Server). This one line command will do the trick.
0sudo kill -9 $( ps -e | grep Xorg | awk '{ print $1 }' ) -
When you run a lot of containers the built in docker ps output becomes unreadable. This command formats the output to be easier on the eyes. Requires q (https://github.com/harelba/q) text as data. Show Sample Output
0docker ps | sed -e 's/ /\+/g' -e 's/CONTAINER ID/CONTAINER_ID/' | tr -s '+' '\t' | q -t 'select c1,substr(c7, 0, 40),c2,c6 from -' | column -t -
If you want to see your top ten cpu using processes from the browser (e.g. you don't want to ssh into your server all the time for checking system load) you can run this command and browse to the machines ip on port 8888. For example 192.168.0.100:8888 Show Sample Output
0while true; do ps aux | sort -rk 3,3 | head -n 11 | cut -c -120 | netcat -l -p 8888 2>&1 >/dev/null; done & -
Applies 'docker rm' to all container IDs that appear in 'docker ps -a' but not in 'docker ps' - i.e. the ones that are not running. Show Sample Output
0$ docker rm `(docker ps -q && docker ps -qa) | sort | uniq -u` -
0docker ps -a | grep 'Exit' | awk '{print $1}' | xargs docker rm
-
I occasionally need to see if a machine is hitting ulimit for threads, and what process is responsible. This gives me the total number, sorted low to high so the worst offender is at the end, then gives me the total number of threads, for convenience.
0(ps -U nms -o pid,nlwp,cmd:500 | sort -n -k2) && (ps -U nms -o nlwp | tail -n +2 | paste -sd+ | bc) -
0PID=$(ps -ef | grep processName | grep -v grep | awk '{print $2'}); kill -9 $PID
-
This prints out a list of all zombie processes PIDs so you can do things like kill the zombies Show Sample Output
0ps axo pid=,stat= | awk '$2~/^Z/ { print $1 }' -
0( ps -U nms -o pid,nlwp,cmd:500 | sort -n -k2) && (ps h -U nms -o nlwp | paste -sd+ | bc)
-
Works on Linux, not other UNIXes
0ps -U user -
0for containerId in $(docker ps | awk '{print $1}' | grep -v CONTAINER); do docker inspect -f "{{ .Name }}" $containerId | sed 's#/##' ; docker port $containerId; done
-
0docker rm $(docker ps -aqf status=exited)
-
Kills all browser tabs, without killing browser or extensions.
0kill $(ps x | grep '\/chrome *.* --type=renderer ' | awk '{print $1}') - ‹ First < 6 7 8 9 10 > Last ›
What's this?
commandlinefu.com 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.
Check These Out
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:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)
- » commands using ps