Hi all,

I can confirm that behaviour too for Firebird 1.0.3 on Linux
(SuperServer).
If any client has connected to the Server, a 'gfix -shut -force x'
will prevent new connections and the actual connections will be
forced off the database.
Nevertheles the DB-Server seems to hold on the database (file?) until
the last application connected to the database has terminated.

That's the reason why I need to shut down the Firebird server to
maintain the database (as I posted some time ago, I need to replace
the actual database file with another one every night). Momentarily
it seems shutting down the database server is the only save method
to force all off the database.

Roger


--- In firebird-support@yahoogroups.com, "Ivan Prenosil"
<Ivan.Prenosil@s...> wrote:

> > gfix -force does prevent new connections and it does prevent existing
> > connections from doing anything. But it seems that the existing
> > connection still keeps a grip on the database file.
>
> I noticed it too, and think it is a bug
> (what is interesting is that if you ask to get list of connections,
> the offending "connection" is not there, so the file is hold for no

reason.)

>
> Ivan
>
> ----- Original Message -----
> From: "nealro" <nealoconnell@m...>
> To: <firebird-support@yahoogroups.com>
> Sent: Friday, June 18, 2004 8:35 PM
> Subject: [firebird-support] GFIX bug?
>
>
> > The -force option for GFIX does not seem to work correctly. As a
> > result, I am not able to automate the backup/restore process. I'm
> > just following the procedure outlined at firebird.sourceforge.net and
> > posting it here first.
> >
> > To reproduce the bug:
> >
> > - use an FB client (I used IBAccess in my test) to connect to a
> > database using a user other than SYSDBA
> > - from a command prompt:
> >
> > gfix -user "SYSDBA" -password "masterkey" -shut -force 0 <database>
> >
> > When GFIX completes, the database connection established in IBAccess
> > can no longer do anything (expected), but when I try to perform a
> > restore to the database using GBAK
> >
> > gbak -R -user "SYSDBA" -password "masterkey" <backup file> <database>
> >
> > I get:
> >
> > gbak: ERROR: could not drop database <database> (database might be in
> > use)
> > gbak: Exiting before completion due to errors
> >
> > If I then close IBAccess, the GBAK call succeeds.
> >
> >
> > gfix -force does prevent new connections and it does prevent existing
> > connections from doing anything. But it seems that the existing
> > connection still keeps a grip on the database file.
> >
> >
> > So I can't reliably automate a database backup/restore. End users
> > have a bad habit of leaving the client application open overnight.
> >
> > I don't know if this is a bug with GFIX or with FBServer.
> >
> >
> > Using FB 1.5.0.4306 (super server) on winXP sp1