2 added 113 characters in body
source | link

Since old times, UNIX philosophy has been "building short, simple, clear, modular, and extendable code", so a super-tool that kills based in port number is way too complicated to maintain, on the other hand, kill was meant to send signals to the process (which happens to end them) not necessarily "to kill" them.

I have searched for a tool that do that, none found that only do that (normally they comes bundled with other tools/functionality or are complex of use). Of course you can use kill -SIGNAL $(lsof -i:port) to send any signal you like.

Since old times, UNIX philosophy has been "building short, simple, clear, modular, and extendable code", so a super-tool that kills based in port number is way too complicated to maintain, on the other hand, kill was meant to send signals to the process (which happens to end them) not necessarily "to kill" them.

I have searched for a tool that do that. Of course you can use kill -SIGNAL $(lsof -i:port) to send any signal you like.

Since old times, UNIX philosophy has been "building short, simple, clear, modular, and extendable code", so a super-tool that kills based in port number is way too complicated to maintain, on the other hand, kill was meant to send signals to the process (which happens to end them) not necessarily "to kill" them.

I have searched for a tool that do that, none found that only do that (normally they comes bundled with other tools/functionality or are complex of use). Of course you can use kill -SIGNAL $(lsof -i:port) to send any signal you like.

1
source | link

Since old times, UNIX philosophy has been "building short, simple, clear, modular, and extendable code", so a super-tool that kills based in port number is way too complicated to maintain, on the other hand, kill was meant to send signals to the process (which happens to end them) not necessarily "to kill" them.

I have searched for a tool that do that. Of course you can use kill -SIGNAL $(lsof -i:port) to send any signal you like.