It's a good idea to glance some docs/manuals (man ss, man netstat) to have some vague memories about what each of these commands can do. Sooner or later you're going to need kill some process to free some port. It hangs in OS in special state - only thing you can do is wait or reboot. It cannot be ignored by processes.Īfter killing process that had opened TCP port it make take a while before this port is closed. The -9 signal is a SIGKILL signal - usually just called kill. This is just "asking" process to exit - similar to alt+f4. Without a name of a signal given default one is used - SIGTERM. Kill (pid) and killall (matching a name) sends signals to processes. You may end up with a surprise ) You can kill some system service like X server, print spooler, OS upgrade process. Depending on the OS it can have some shortcuts to kill.Īs to root and sudo I would be very careful. top on the other hand does not show open ports. There are tons of tutorials about these two commands. Ss -tnlp and netstat -tnlp shows pid of processes, their names and their open/listening (aka server) ports. 9 for forceful killing in both kill and killall
Here are the steps for Linux (courtesy of mayankjoshi) Run the first command again to see if it's closed. If it's still running, try this:įirst, try this (replace typeyourPIDhere with the number you copied above): However, if it returns some input, try to kill it with:Īgain, try to connect. If it returns immediately with no output, the port isn't open. Now, test if it's closed by connecting to the port (replace portNumber with the actual port number): This will give you a response as follows - copy the PID number for the next step:įirst, try this (replace PID with the number you copied above):
Find the process ID (PID) of the port (replace the 'portNumber' with the number)
This is a thing I need to google every now and then so here's a simple recipe for closing neglected ports on MacOS, Windows and Linux.ġ.
0 kommentar(er)
