Hi All,

Not that long ago I changed a client over from superserver to
classic - Firebird v1.5 (I still have not managed to change up
to FB v2.x).

It has all gone very well... except that we do seem to be
getting some of the processes left behind when the actual
network session / client-app is gone. (I am not certain
whether processes belong to applications that died unexepctedly
etc... it seems likely.)

After a week or so on the server there may be 20 or so FB
classic processes sitting there waiting for me to kill them.

FB v1.5 classic running on Windows 2000 SP4

Note that, for various reasons, the classic executable
has been renamed. I am wondering if this may be the cause?
(Seems unlikely but thought I should mention it.)

Anyone else see this?

Are there any tools out there that make it easier to try and
manage a FB classic v1.5 install? (For example to extract the
process-to-ip-address-to-ip-addess information, even better if
it could eventually work out the terminal server session and
user that is using the process. AFAICT all the information is
available, it just needs and tool to put it all together.)

--
Geoff Worboys
Telesis Computing