Commands tagged process (48)
-
If you really _must_ use a loop, this is better than parsing the output of 'ps': PID=$! ;while kill -0 $PID &>/dev/null; do sleep 1; done kill -0 $PID returns 0 if the process still exists; otherwise 1
0wait -
Col 1 is swapped sum in kb Col 2 is pid of process Col 3 is command that was issued Show Sample Output
0for i in $(ps -ef | awk '{print $2}') ; { swp=$( awk '/Swap/{sum+=$2} END {print sum}' /proc/$i/smaps ); if [[ -n $swp && 0 != $swp ]] ; then echo -n "\n $swp $i "; cat /proc/$i/cmdline ; fi; } | sort -nr -
just a leaner, smaller version. Love the original idea!
0kill -9 `ps xawo state=,pid=|sed -n 's/Z //p'` -
0echo $(($(ulimit -u)-$(pgrep -u $USER|wc -l))
-
0TOTAL_RAM=`free | head -n 2 | tail -n 1 | awk '{ print $2 }'`; PROC_RSS=`ps axo rss,comm | grep [h]ttpd | awk '{ TOTAL += $1 } END { print TOTAL }'`; PROC_PCT=`echo "scale=4; ( $PROC_RSS/$TOTAL_RAM ) * 100" | bc`; echo "RAM Used by HTTP: $PROC_PCT%"
-
0watch 'mysql -e "show full processlist;"'
-
Inner "ps...grep..." command searches for a process matching the specified . "lsof -p lists all file descriptors owned by . Includes open files, sockets, devices, etc... Show Sample Output
0sudo lsof -p `sudo ps aux | grep -i neo4j | grep -v grep | awk '{ print $2 }'` -
Good because it doesn't use Sed.
0python -c "a='$(ps -u luke | grep Viber.exe)';b= a.split(' ')[1];import os;os.system('cpulimit -l 1 -p '+b)" -
List the busiest scripts/files running on a cPanel server with domain showing (column $12). Show Sample Output
0/usr/bin/lynx -dump -width 500 http://127.0.0.1/whm-server-status | grep GET | awk '{print $12 $14}' | sort | uniq -c | sort -rn | head -
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 }' -
0pgrep -lf processname | cut -d' ' -f1 | awk '{print "cat /proc/" $1 "/net/sockstat | head -n1"}' | sh | cut -d' ' -f3 | paste -sd+ | bc
-
0watch -n 0.5 ps -C <processname>
-
0awk '/VmSwap/{print $2 " " $3}' /proc/$PID/status
-
options "sleep" in seconds "--verbose" show "full" processlist Show Sample Output
0mysqladmin -u user -ppassword --verbose processlist --sleep 1 -
This command is better for just displaying the memory in KiB. Show Sample Output
0ps -eo size,command --sort -size | head -
to kill, use `kill PID` Credit: user Craig Ringer on stackexchange.com, recommends to kill the process rather than deleting postmaster.pid when there is an orphan Postgresql server process. Show Sample Output
0cat /usr/local/var/postgres/postmaster.pid -
May need to substitute 'awk' for 'gawk'.
0ps axo state,ppid | awk '!/PPID/$1~"Z"{print $2}' | xargs -r kill -9 -
The sample output is from an Android Device Show Sample Output
0grep -e AnonHugePages /proc/*/smaps | awk '{ if($2>4) print $0} ' | awk -F "/" '{system("cat /proc/" $3 "/cmdline");printf("\n");print $0; printf("\n");}' -
Lower PowerShell priority, so that to launch processes in the background and work normally with other applications Show Sample Output
0PS> Get-WmiObject Win32_process -filter 'name = "powershell.exe"' | Foreach-Object { $_.SetPriority(16384) } -
-1lsof -p <process_id> | wc -l
-
The '[r]' is to avoid grep from grepping itself. (interchange 'r' by the appropriate letter) Here is an example that I use a lot (as root or halt will not work):
while (ps -ef | grep [w]get); do sleep 10; done; sleep 60; haltI add the 'sleep 60' command just in case something went wrong; so that I have time to cancel. Very useful if you are going to bed while downloading something and do not want your computer running all night.-2while (ps -ef | grep [r]unning_program_name); do sleep 10; done; command_to_execute -
Did some research and found the previous command wrong, we don't kill a zombie but its parent. Just made some modifcation to khashmeshab's command.
-4ps -xaw -o state,ppid | grep Z | grep -v PID | awk '{ print $2 }' | xargs kill -9 -
There's already a proper command for what the former alternative tried to script
-5pkill $1 - < 1 2
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 tagged process