Subject 1.5.4 classic subprocesses and tcp sockets
Author Mitch Peek
When running Firebird with multiple connections, each sub-process
handles the task but the tcp stack identifies the master pid as the
owner of the socket.

As part of troubleshooting, we wish to identify which connection is
being used by the individual sub-process. The windows tcp stack does
not know, how can Firebird report this back?

Or in other words, how can I identify the user/socket when Firebird
spawns a new process?