Commands using ps (300)
-
0ps aux | awk '{if ($5 != 0 ) print $2,$5,$6,$11}' | sort -k2rn | head -10 | column -t
-
This command is better for just displaying the memory in KiB. Show Sample Output
0ps -eo size,command --sort -size | head -
If you have many port mappings, docker ps output becomes pretty illegible. The ~120 char one-liner changes the output into a more readable list of container! Show Sample Output
0docker ps | perl -ple "s/\$/\n\n/g;s/\s{2,}/\n/g;s/(Up)/\\e\[32m\$1\\e\[0m/g;s/(Down)/\\e\[31m\\e\[5m\$1\\e\[25m\\e\[0m/g;s/^([^\n]+)/\\e\[1m\$1\\e\[0m/g;s/(\w+?)$/\\e\[4m\$1\\e\[24m/g" | more -
0ps axno user,tty | awk '$1 >= 1000 && $1 < 65530 && $2 != "?"' | sort -u
-
Show the executable that spawned the process and show the PID and ORACLE_HOME relative to the environment within which the process is running.
0ps -ef | grep [p]mon | awk '{print $2}' | xargs -I {} ps eww {} | awk '{print $1 " " $5 " " $6 " " $0}' | sed 's/\(S*\) \(S*\) .*ORACLE_HOME/\1 \2/g' | cut -f1,2,3 -d" " -
Useful if your Docker host starts running out of disk space due to Docker debris. You should start by running "sudo docker ps" in order to check that all required containers are in fact running, and fix any that aren't before proceeding to the main event! "sudo docker rm $(sudo docker ps -q -f status=exited)" removes all containers which are no longer running. "sudo docker rmi $(sudo docker images -q -f dangling=true)" removes all Docker images not required for currently running containers.
0sudo docker rm $(sudo docker ps -q -f status=exited); sudo docker rmi $(sudo docker images -q -f dangling=true) -
0processid=$(ps aux | grep 'nginx' | grep -v grep| awk '{print $2}')
-
Continuously watches postgres, showing the instances using the most RAM at the top. Show Sample Output
0watch -n 1 '{ ps aux | head -n 1; ps aux --sort -rss | grep postgres | grep -v grep; } | cat' -
alternative to pidof command Show Sample Output
0processid =$(ps aux | grep 'ProcessName' | grep -v grep| awk '{print $2}') -
This command shows you how much is RSS utilization and real memory Show Sample Output
0ps aux | awk '{sum+=$6} END {print sum / 1024}' -
0ps -ef |grep oracle |grep pmon |awk '{print $2}' |xargs -I {} ps eww {} |grep pmon |grep -v grep |awk '{print $5 " " $6 " " $0}' |sed 's/\(S*\) \(S*\) .*ORACLE_HOME/\1 \2/g' |cut -f1,2,3 -d" " 2010-03-23 20:36:59 User:
-
0ps -C httpd -o rss --no-headers | awk '{SUM += $1} END {printf("%.0f\n",SUM/1024)}'
-
Usefull, for example, when many ports are exposed and the docker ps output looks cluttered. Show Sample Output
0alias dockps='docker ps --format "table {{.ID}}\t{{.Image}}\t{{.Status}}\t{{.Names}}"' -
The classical 'ps aux | grep' can do this with one more parameter, the '-v', with means 'NOT' to grep.
0ps aux | grep -v name_you_want_to_hide -
No need for grep or xargs
0ps auxw | awk '/(apache|httpd)/{print"strace -F -p " $2}' | sh -
May need to substitute 'awk' for 'gawk'.
0ps axo state,ppid | awk '!/PPID/$1~"Z"{print $2}' | xargs -r kill -9 -
passin list of docker container IDs to docker stop Show Sample Output
0docker stop $(docker ps -a -q) -
Get the last run container ID and stop it.
0docker stop $(docker ps -lq) -
0ps -eo pcpu,pmem,cmd | grep Service| grep -v grep| sort -k 1 -nr | head -5
-
Useful when developing and you donut usually have other docker commands running Show Sample Output
0docker kill $(docker ps -q) -
-1ps awwux|awk '{print $1}'|sort|uniq
-
-1ps -u<user>
-
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).
-1ps -o euid,egid --ppid `netstat --inet --inet6 -pln|awk '/:80 / { split($7,tmp, "/"); print tmp[1]; }'`|sort |uniq|grep -v EUID -
-1ps -eo args,%cpu | grep -m1 PROCESS | tr 'a-z-' ' ' | awk '{print $1}'
-
-1ps -C apache o pid= | sed 's/^/-p /' | xargs strace
- ‹ First < 8 9 10 11 12 >
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