Commands using ps (300)
-
0ps aux | grep salt | awk '{ print $2}' | xargs kill
-
I like this method because I can make use of pgrep which also has the -f flag that can use regex to match patterns in the full command line string. It will also do ps -fww on all pids returned by pgrep, providing a list of process matching the regex provided. Show Sample Output
0ps -fwwp $(pgrep process_name) -
0watch -n 0.5 ps -C <processname>
-
0ps -auxh | sed -r "s/\s+/ /g" | cut -d ' ' -f 1 | sort | uniq -c | sort -gr
-
0ps -auxf | sort -nr -k 4 | head -10
-
0docker ps -a | grep Exit | awk -F " " '{ print $1 }' | xargs docker rm {}
-
0docker ps -a | grep "Exited" | awk '{print $1}' | xargs docker rm
-
tested on solaris 10
0ps -e | awk '$4~/<process name>/{print $1}' |xargs gcore -o ~/troubleshooting -
0docker stop $(docker ps -a -q)
-
0ls -1 /proc/$(ps ax | grep <Process Name> | head -n 1 | awk '{print $1;}')/task | tail -n +2
-
0ps m
-
0dockexecl() { docker exec -i -t $(docker ps -l -q) bash ;}
-
0docker inspect --format "{{ .NetworkSettings.IPAddress }}" $(docker ps -q)
-
On debian parent process is running as root, workers as www-data. You can run strace in backgroud, get its PID, curl your webpage, kill strace and read your stats.
0strace -c $(ps -u www-data o pid= | sed 's/^/-p/') -
0ps -eo comm,pcpu --sort -pcpu | head
-
0alias dps='docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"'
-
Use pgrep's flexibility to search for processes, with pretty formatting via ps. All parameters are passed to pgrep. Show Sample Output
0psg() { ps -f fwwp $(pgrep $*) 2>/dev/null } -
0ps -eo pmem,comm | grep chrome | cut -d " " -f 2 | paste -sd+ | bc
-
process name , process id , xms( initial memory allocation pool) , xmx(maximum memory allocation pool) Show Sample Output
0ps -ef | grep jav[a] | awk '{print substr($1,1),substr($2,1),substr($0,index($0,"-Xms"),7),substr($0,index($0,"-Xmx"),7)}' -
0docker rm $(docker ps -a -q)
-
Stop all docker containers
0docker stop $(docker ps -a -q) -
0docker stats --no-stream $( docker ps -q ) | sed -e "$( docker ps --format "{{.ID}} {{.Names}}" | sed -e "s/\(.*\) \(.*\)/s\/\1\/\2\t\/g;/" )"
-
0ps -ef | grep -oh 'Xmx[0-9]*' | cut -d'x' -f2 | awk '{SUM += $1} END { print SUM}'
-
0ps -u jboss -o nlwp= | awk '{ num_threads += $1 } END { print num_threads }'
-
Given a process name (kdiff3 in this example) that keeps auto-spawning/starting, auto-kill until it stops, assuming there is an upper limit (if not, reboot). This was beneficial after I clicked the DIFF button in a git GUI on a merge commit. 2000+ files were being opened one after the other in my diff program (kdiff3). Each time I closed one (or quit Kdiff3), the next file would be auto-opened in Kdiff3.
0while [ ! -z $(ps -A | grep -m1 kdiff3 | awk '{print $1}') ]; do kill -9 $(ps -A | grep -m1 kdiff3 | awk '{print $1}'); sleep 1; done - ‹ First < 7 8 9 10 11 > 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