Subject RE: [Newsletter] Re: [firebird-support] run firebird engine without fbguard
Author Yassir Kozha
Hello again,

Thank you for the answer. However I was not able to find a way to run firebird engine as Superserver without fbguard on linux environment.
The firebird engine couldn’t be started using the binary of the firebird (/usr/sbin/firebird). It just freezes.

Regards
Yassir

From: firebird-support@yahoogroups.com<mailto:firebird-support@yahoogroups.com> <firebird-support@yahoogroups.com<mailto:firebird-support@yahoogroups.com>>
Sent: Saturday, July 13, 2019 2:10 AM
To: firebird-support@yahoogroups.com<mailto:firebird-support@yahoogroups.com>
Subject: *EXT* [Newsletter] Re: [firebird-support] run firebird engine without fbguard



Yassir Kozha wrote:

> We currently use fbguard to run the firebird engine as recommended in the docs of firebird.

> Systemd service unit:
> ‘ExecStart=/usr/sbin/fbguard -daemon -onetime’

>

> The problem with this approach is that when killing the firebird
> engine process ‘SIGKILL’, the fbguard exites with ‘0’. In this case
> systemd doesn’t get that the firebird process was terminated abnormally.

[..]
>

> Is it possible to run firebird engine as a daemon without the use of fbguard?

The Guardian is an optional process for Superserver and SuperClassic.
If enabled, it watches the firebird server process and restarts it if
it fails for some reason. Guardian is not applicable to Classic at
all.

I don't have the knowledge to give you the script to run the server
without fbguard in the Linux/systemd environment but, on Windows, you
simply remove the Guardian service and the Firebird server process
will then run independently. The way to achieve the same in your
environment is probably just as simple - I hope you will ask
again with a targeted question if you need help with this. I think you
might get some clues from the install script, if you installed from
the official Firebird kit.

Helen

>

> Kind regards,
> Yassir

>
>
>
>
>

--
Best regards,
Helen mailto:helebor@...

---
This email has been checked for viruses by AVG.
https://www.avg.com



[Non-text portions of this message have been removed]