Commands using awk (1,418)
-
Ok so it's rellay useless line and I sorry for that, furthermore that's nothing optimized at all... At the beginning I didn't managed by using netstat -p to print out which process was handling that open port 4444, I realize at the end I was not root and security restrictions applied ;p It's nevertheless a (good ?) way to see how ps(tree) works, as it acts exactly the same way by reading in /proc So for a specific port, this line returns the calling command line of every thread that handle the associated socket
-5p=$(netstat -nate 2>/dev/null | awk '/LISTEN/ {gsub (/.*:/, "", $4); if ($4 == "4444") {print $8}}'); for i in $(ls /proc/|grep "^[1-9]"); do [[ $(ls -l /proc/$i/fd/|grep socket|sed -e 's|.*\[\(.*\)\]|\1|'|grep $p) ]] && cat /proc/$i/cmdline && echo; done -
Just find out the daemon with $ netstat -atulpe. Then type in his name and he gets the SIGTERM.
-5kill_daemon() { echo "Daemon?"; read dm; kill -15 $(netstat -atulpe | grep $dm | cut -d '/' -f1 | awk '{print $9}') }; alias kd='kill_daemon -
I don't know if it's better but works fine :)
-5awk '{if (NR == 3) print}' <file> -
-5ps aux|grep -i [p]rocessname|awk '{ print $2 }'|xargs kill
-
-5awk 'END {print NR}' /etc/passwd
-
-6awk '{if (NR % 2 == 1) print $0}' file.txt
-
Check if Fail2Ban is running on the system and alert it with a message in the terminal Show Sample Output
-6FAIL2BAN=`ps ax | grep fail2ban | grep -v grep | awk {'print $1'}` && if [ -n "$FAIL2BAN" ]; then printf "\n[INFO] Fail2Ban is running and the PID is %s\n\n" $FAIL2BAN; else printf "\n [INFO] Fail2Ban is not running\n\n"; fi -
search_criteria = what do you want to kill pid = pid of you dont kill
-6kill -9 `ps aux | grep "search_criteria" | awk '{if ($2 != pid) print $2}'` -
Removed unneeded grep -v by making the initial grep unable to match itself.
-6ps -ef | grep [j]boss | awk '{print $2}'|xargs kill -9 -
get the ip address on your LAN Show Sample Output
-6ifconfig |grep broadcast | awk '{print $2}' -
-6ps -ef | grep PROCESS | grep -v grep | awk '{system "kill -9" $2}
-
This is a nice way to kill processes.. the example here is for firefox!!! substitute firefox for whatever the process name is... Show Sample Output
-7ps aux | grep -i firefox | grep -v grep | awk '{print $2}' | xargs -t -i kill -9 {} -
-7ps auxwww | grep outofcontrolprocess | awk '{print $9}' | xargs kill -9
-
This command kills all processes with 'SomeCommand' in the process name. There are other more elegant ways to extract the process names from ps but they are hard to remember and not portable across platforms. Use this command with caution as you could accidentally kill other matching processes! xargs is particularly handy in this case because it makes it easy to feed the process IDs to kill and it also ensures that you don't try to feed too many PIDs to kill at once and overflow the command-line buffer. Note that if you are attempting to kill many thousands of runaway processes at once you should use 'kill -9'. Otherwise the system will try to bring each process into memory before killing it and you could run out of memory. Typically when you want to kill many processes at once it is because you are already in a low memory situation so if you don't 'kill -9' you will make things worse
-7ps axww | grep SomeCommand | awk '{ print $1 }' | xargs kill -
-8ps -ef | awk -v OFS="\n" '{ for (i=8;i<=NF;i++) line = (line ? line FS : "") $i; print NR ":", $1, $2, $7, line, ""; line = "" }'
-
This works just like write or wall ... cept one thing the sender is anonymous ... if you really want to drive everyone insane replace echo \"The Matrix has you...\" with cat /dev/urandom nice one to do on April fool's day Show Sample Output
-12w | egrep -v '(load|FROM)' | awk '{print $2}' | sed 's/^/tty/' | awk '{print "echo \"The Matrix has you...\" >> /dev/" $1}' | bash -
get the ip address on your LAN Show Sample Output
-12ifconfig |grep broadcast | awk '{print $2}' -
-14for i in $(grep 'mystring' myfile1)|awk '{print $1}'); do grep $1 myfile2;done
- ‹ First < 55 56 57
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 awk