What do "local connections" actually mean? Function call interface or
a TCP port for local usage only?

I have a situation where there is a separate client application
connected to the Firebird server port on the same machine, and the
task is to shutdown both cleanly. I have also a windows service
executable starting/stopping both the client and Firebird.

It would be possible to embed Firebird in the service executable, but
*not* the client application. Naturally this would work only if the
embedded Firebird actually provides a port to connect to.

Ari

--- In firebird-support@yahoogroups.com, "Richard Pendered"
<rpendered@t...> wrote:

> Sounds like you need to use the embeded version of FB whcih starts

with the

> app and stops with the app automatically. The only down side is that

it is

> limited to local connections (which should be fine).
>
> -----Original Message-----
> From: Klement Guenther - Munich-MR [mailto:gklement@m...]
> Sent: 20 October 2003 07:25
> To: firebird-support@yahoogroups.com
> Subject: AW: [firebird-support] Command line options
>
>
>
> > Actually what my requirement is that I want to start fbserver
> > whenever my
> > client application starts and stop it when the user quits the client
> > application. It should be very much transparent to the
> > client. Therefore,
> the fbserver should have an option to handle the shutdown well.
>
> There seems to be a need for an autostop option in fbserver, Isn't it?
>