|
From: SourceForge.net <no...@so...> - 2004-03-11 17:13:16
|
Bugs item #914240, was opened at 2004-03-11 10:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109028&aid=914240&group_id=9028 Category: IBGuardian Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mark Ericksen (mericksen) Assigned to: Nobody/Anonymous (nobody) Summary: Need Service dependencies to keep running longterm Initial Comment: I think this applies to FBGuradian and FBServer both. I recommend adding Windows service dependencies for the windows implementation. The issue is that in certain circumstances (like a Windows update/patch) the boot order of various Windows services can change. This means that the service called "lanmanserver" (which is displayed as "Server") which initializes the networking stack in Windows may be changed to start AFTER Firebird starts. This means Firebird cannot bind to the socket because it hasn't been initialized yet. This happens to some of our clients occassionally and would not happen if a service dependency existed. My applications run as services also and *must* access Firebird through TCP connection. To make my applications usable with Firebird or Interbase I've let the service dependencies be defined from a config file so it can be changed if needed. Something similar might be helpful with Firebird. It believe it would fix the issues that I've encountered. -Mark E. PS> Excellent work with Firebird. It is now my DB of choice for embedded applications. Great job! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109028&aid=914240&group_id=9028 |