Re:Bash Shell Awesomeness - Mass Killing Processes (On Ubuntu)
by jgrahamc on Thursday August 06, 2009 @08:58AM
(#745345)
Actually, I can never remember any of the options. I find myself doing man FOO all the time and usually work under the assumption that there's probably already an option to do the thing I'm trying to do.
Kudos to the original poster. That sort of combining of small tools is what the NIX command-line is all about.
Re:Bash Shell Awesomeness - Mass Killing Processes (On Ubuntu)
by ajross on Thursday August 06, 2009 @11:51AM
(#745719)
Who modded that down? He really should be using awk instead of cut. It has better readability: "{print $2}" to print the second field vs. a set of magic numbers denoting a character field. It's vastly easier to write (again, the "second field" is intuitive). It's also more generally useful, meaning that it's a better tool to know; cut is very primitive.
That said, there are better ways still to solve this problem. Some of them were detailed above. One that wasn't was the fact that GNU ps has lots of filtering options itself, in this case:
ps -eo pid -U 1002
Does the work of the grep and cut from the original for you.
http://linux.die.net/man/1/killall
Hehe... That reminds me of the day I learned that you shouldn't put . in your path, especially in the front.
It turns out that (old?) Red Hat machines had a script 'killall' in their /etc/init.d ...
I must use killall 100 times a day :)
So much good stuff in there.
Good reminder to do a periodic review of that stuff, not all the options are easy to remember if you don't use them frequently enough.
Kudos to the original poster. That sort of combining of small tools is what the NIX command-line is all about.
That said, there are better ways still to solve this problem. Some of them were detailed above. One that wasn't was the fact that GNU ps has lots of filtering options itself, in this case:
Does the work of the grep and cut from the original for you.You don't want charaters this to that, what you do want is column 2.