| Subject | Re: run firebird engine without fbguard |
|---|---|
| Author | |
| Post date | 2019-07-15T10:16:51Z |
First of all I do not understand initial problem:
> The problem with this approach is that when killing the firebird engine process ‘SIGKILL’
When firebird server is killed with any signal except 2 & 15 it's restarted by guardian, i.e. guardian does not exit.
tro:~/firebird/HEAD/gen/Debug/firebird$ ps ax| grep firebird 6776 ? S 0:00 /home/alex/firebird/HEAD/gen/Debug/firebird/bin/fbguard -daemon -forever
6777 ? Sl 0:00 /home/alex/firebird/HEAD/gen/Debug/firebird/bin/firebird
6782 pts/18 S+ 0:00 grep --color=auto firebird
alex@vostro:~/firebird/HEAD/gen/Debug/firebird$ kill -SIGKILL 6777
alex@vostro:~/firebird/HEAD/gen/Debug/firebird$ ps ax| grep firebird
6776 ? S 0:00 /home/alex/firebird/HEAD/gen/Debug/firebird/bin/fbguard -daemon -forever
6786 ? Sl 0:00 /home/alex/firebird/HEAD/gen/Debug/firebird/bin/firebird
6791 pts/18 S+ 0:00 grep --color=auto firebird
alex@vostro:~/firebird/HEAD/gen/Debug/firebird$
6777 ? Sl 0:00 /home/alex/firebird/HEAD/gen/Debug/firebird/bin/firebird
6782 pts/18 S+ 0:00 grep --color=auto firebird
alex@vostro:~/firebird/HEAD/gen/Debug/firebird$ kill -SIGKILL 6777
alex@vostro:~/firebird/HEAD/gen/Debug/firebird$ ps ax| grep firebird
6776 ? S 0:00 /home/alex/firebird/HEAD/gen/Debug/firebird/bin/fbguard -daemon -forever
6786 ? Sl 0:00 /home/alex/firebird/HEAD/gen/Debug/firebird/bin/firebird
6791 pts/18 S+ 0:00 grep --color=auto firebird
alex@vostro:~/firebird/HEAD/gen/Debug/firebird$
You see - firebird process is restarted,
> the
fbguard exites with ‘0’. In this case systemd doesn’t get that the firebird process was terminated abnormally.
That's abnormal behavior. What is the source of binaries with which you observe it?
What about running firebird server w/o guardian - well, server does not contain code to daemonize itself, i.e. you will have to perform all required for it activity yourself. In other aspects - why not, certainly you can.