shell script to kill processes running on port number

varunbihani · 12-05-2005, 11:19 PM

I need a shell script that will find all the processes running on particular port number and then I want to kill those processes

Cmd1: lsof -i : <portnumber> (it will return the process ID)
cmd2: kill -9 <process ID>

plz help

blindcoder · 12-06-2005, 01:50 AM

Quote:

Originally Posted by varunbihani

Cmd1: lsof -i : <portnumber> (it will return the process ID)
cmd2: kill -9 <process ID>

Code:

kill `lsof -i :80 | tail -n +2 | sed -e 's,[ \t][ \t]*, ,g' | cut -f2 -d' '`

You don't really want to kill -9 immediately. Give the program a chance to shut down cleanly.

Quote:

Originally Posted by varunbihani

plz help

Oh, and most people prefer the english word "please", thank you very much.

Greetings,
Benjamin

varunbihani · 12-06-2005, 01:52 AM

Thanks A lot for the script.. Can you also explain this command??

blindcoder · 12-06-2005, 02:10 AM

Quote:

Originally Posted by blindcoder

Code:

kill `lsof -i :80 | tail -n +2 | sed -e 's,[ \t][ \t]*, ,g' | cut -f2 -d' '`

Everything between two backticks (`) will be replaced by the output of the command between them.
In this case, this will be executed first:

Code:

lsof -i :80 | tail -n +2 | sed -e 's,[ \t][ \t]*, ,g' | cut -f2 -d' '

So first "lsof -i :80" will be run. Its output will be piped to tail -n +2 which cuts off the first line, which we don't need. The rest will be piped to sed which in this case will truncate all spaces/tabs to one space only for easier parsing. This text is then piped to cut which in this case will print only the second column delimited by a single space (which we created using sed a step earlier). The output will then be all the PIDs without the rest.
Since all this happens within backticks (`) the output from cut will then be inserted in the first command which will then look like this (for example):

Code:

kill 12435 8923 21349

Greetings,
Benjamin.

Emmanuel_uk · 12-06-2005, 02:12 AM

man lsof
man sed
man tail
man cut
google linux pipe
Then if you have a question I am sure people will help further

blindcoder · 12-06-2005, 02:17 AM

Quote:

Originally Posted by Emmanuel_uk

man lsof
man sed
man tail
man cut
google linux pipe
Then if you have a question I am sure people will help further

*sigh* there goes the oh-so-helpful linux community down the drain...
Posts like yours are the reason why I often hear statements along these lines:
The Linux community isn't helpful at all!
All they tell you is to use google! I can tell that myself.

And others like that. Please, if you don't have anything productive to say, just shut the fuck up, thanks.

Benjamin

Emmanuel_uk · 12-06-2005, 02:20 AM

not meant to be offensive. Just see my other 500 posts.
Was going to help if question was clearer
Also missed your answer when I posted
By posting I registered on that thread
Do not be so assuming, and mind your language

blindcoder · 12-06-2005, 02:24 AM

whoo, you have more posts than me, I bow before you.
I fail to see where the question was unclear, but maybe that's just me.

Greetings,
Benjamin

Emmanuel_uk · 12-06-2005, 02:35 AM

Listen, I have jsut made an appology, you could just please do the same.
No need to be sarcky ok?
If you had checked my posts to see what kind of help I give, you
would not have posted what you just did.

>>Can you also explain this command??
Was not sure what the guy did not understand and where he needed help

Also I explained that I did not see your post. I know I am daft

Ok, peace

Emmanuel_uk · 12-06-2005, 02:35 AM

[double posted same text happy clicking problem] deleted

blindcoder · 12-06-2005, 03:50 AM

Sorry for it all, but I really get sick at "use google to find out" posts because I keep seeing them literally everywhere I go. So called "help" channels on IRC, mailing lists, newsgroups, everywhere.

I'm sorry to have it taken out on you.

Greetings,
Benjamin

Emmanuel_uk · 12-06-2005, 07:57 AM

Thanks. I know, sorry here as well. I was wondering when I was posting about my googling advice being "sane", but I had posted quite a few hints/help to people already, and was running out of steam.
Sometimes script questions are from students, so I tend to want to know what is unclear or expect some homework first.
plz is a good indication of studenthood / younger people. I do not say we have one here, though.

At the same time you had given a great one liner answer
for a *not* such a simple question (IMHO) where one would have expected whoever posted the question to be able to understand / search to understand, not fishing for information / help in that way

Anyhow, I am waffling. This is on top of what I wrote before.

I know googling is not always a suitable message.
Maybe you are kinder, and I am more cynical ?

Nevermind, this is all settled. You know where I come from, and I understand your googlite frustration with non helpful comments

dbogdan · 12-06-2005, 08:41 AM

Quote:

Originally Posted by blindcoder

Everything between two backticks (`) will be replaced by the output of the command between them.
In this case, this will be executed first:

Code:

lsof -i :80 | tail -n +2 | sed -e 's,[ \t][ \t]*, ,g' | cut -f2 -d' '

So first "lsof -i :80" will be run. Its output will be piped to tail -n +2 which cuts off the first line, which we don't need. The rest will be piped to sed which in this case will truncate all spaces/tabs to one space only for easier parsing. This text is then piped to cut which in this case will print only the second column delimited by a single space (which we created using sed a step earlier). The output will then be all the PIDs without the rest.
Since all this happens within backticks (`) the output from cut will then be inserted in the first command which will then look like this (for example):

Code:

kill 12435 8923 21349

Greetings,
Benjamin.

Wow! Now that is a truely helpful post. I've been looking to do something similar to this but was kinda stumped... this detailed breakdown made a little light in my head go BING!... and saved me potentially hours of time searching Google and man pages.

Dave

Emmanuel_uk · 12-06-2005, 08:46 AM

something good out of this discussion then

the one liner gets real credit, which is due