From a689c9bc65908e18ea89b9f5e8ae61b497781e01 Mon Sep 17 00:00:00 2001 From: architeuthidae Date: Fri, 22 Nov 2024 11:16:12 +0100 Subject: [PATCH] doc: Windows netstat fix --- doc/manual/faq.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/manual/faq.rst b/doc/manual/faq.rst index 147ed005a..a53c9c32c 100644 --- a/doc/manual/faq.rst +++ b/doc/manual/faq.rst @@ -145,9 +145,11 @@ You can use the command ``netstat`` to list the ports currently in use on your s $ netstat -anp --inet | grep "" $ lsof -i: -On Windows, use :: +On Windows, you can list ports with: :: - $ netstat -ano -p ip | find "" + $ netstat -ano -p TCP + +Use your preferred method to search through the output; suitable commands will vary by environment (e.g. ``grep`` in an MSYS2 shell, ``Select-String`` in PowerShell, ``find`` in the Windows command line, etc.) In all cases, if there are no results, the port isn't in use and should be free for new processes. @@ -160,7 +162,7 @@ Otherwise, either the running process must be stopped, or you'll have to set dif On Windows, use ``netstat`` again to identify the process ID, and then feed it into ``taskkill``, e.g.: :: - $ netstat -ano | find "" + $ netstat -ano -p TCP $ taskkill /F /PID diagnose and fix sequence errors?