Mitch,

> 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?

Such functionality is part of the Monitoring tables features, which is
part of the v2.1 Firebird release.


Sean