Sometimes stopping Windows Service on Firebird Classic 2.5.0 can leave one or more instances of fb_inet_server.exe running.
This is highly undesirable, since it could lead one to think the database file isn't in use as the service status is "Stopped". A database file copy or file-level backup in this state can corrupt the database (actually this DID occur once with me, and that's why I flagged this issue as "critical").
The correct behavior should be:
- (preferred) The service STOPS, no more instances left running and all database files closed ; *OR*
- The service DON'T STOP, returning an error message.
Currently, running a
taskkill /im fb_inet_server.exe /f
can surely kill every zombie process, but I don't know how harmful this can be.