One script: Get-NetTCPConnection -State Listen, Get-NetUDPEndpoint, the processes that hold the sockets, and Win32_Service's PIDs.
A process that runs exactly one service is attributed to it. A shared svchost runs several, and Windows does not say which of them holds the socket, so it is attributed to none.
http.sys sockets (WinRM, IIS, SMB) belong to the System process.
The fixture is synthetic. There is no Windows host to test against. tools/harvest.py now records this script's output too. For NetOrk/netork#673.
One script: `Get-NetTCPConnection -State Listen`, `Get-NetUDPEndpoint`, the processes that hold the sockets, and `Win32_Service`'s PIDs.
- A process that runs exactly one service is attributed to it. A shared svchost runs several, and Windows does not say which of them holds the socket, so it is attributed to none.
- http.sys sockets (WinRM, IIS, SMB) belong to the System process.
**The fixture is synthetic.** There is no Windows host to test against. `tools/harvest.py` now records this script's output too. For NetOrk/netork#673.
One script: Get-NetTCPConnection -State Listen, Get-NetUDPEndpoint, the
processes holding them and Win32_Service's PIDs. A process running one
service names it; a shared svchost runs several, and which of them holds
the socket Windows does not say, so it names none. http.sys sockets
(WinRM, IIS, SMB) belong to the System process.
The fixture is synthetic: no Windows host was at hand. tools/harvest.py
records the real output. For netOrk#673.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
One script:
Get-NetTCPConnection -State Listen,Get-NetUDPEndpoint, the processes that hold the sockets, andWin32_Service's PIDs.The fixture is synthetic. There is no Windows host to test against.
tools/harvest.pynow records this script's output too. For NetOrk/netork#673.