Classic: Stopping Windows Service leaves one or more instances of fb_inet_server.exe running --------------------------------------------------------------------------------------------
Key: CORE-3622 URL: http://tracker.firebirdsql.org/browse/CORE-3622 Project: Firebird Core Issue Type: Bug Components: Engine Affects Versions: 2.5.0 Environment: Windows Server 2003 / SP2 / x86 Reporter: F.D.Castel Priority: Critical 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel