Subject | Re: [firebird-support] Shutting down Firebird when using classic server on Windows |
---|---|
Author | Helen Borrie |
Post date | 2005-11-23T22:17:35Z |
At 02:22 PM 23/11/2005 +0000, you wrote:
connections (as is the case with Superserver) the only way (for Classic) is
to perform a forced shutdown of the database using gfix -shut -force
nnn. Eventually, all of the client processes will be terminated and any
unprepared clients will get network exceptions and lose their uncommitted work.
Don't use FbGuard with Classic or you run the risk of accumulating ghost
connections. And don't stop the main fb_inet_server service if there are
still client processes running. Just keep the database in shutdown mode (=
offline) until you are ready to reopen the shop.
./heLen
>Stopping the Firebird service doesn't seem to stop theSince the Classic service is not a service that is being shared by all
>fb_inet_server.exe processes for currently active users. How to I
>ruthlessly terminate user connections when running classic server
>under Windows.
connections (as is the case with Superserver) the only way (for Classic) is
to perform a forced shutdown of the database using gfix -shut -force
nnn. Eventually, all of the client processes will be terminated and any
unprepared clients will get network exceptions and lose their uncommitted work.
Don't use FbGuard with Classic or you run the risk of accumulating ghost
connections. And don't stop the main fb_inet_server service if there are
still client processes running. Just keep the database in shutdown mode (=
offline) until you are ready to reopen the shop.
./heLen