06.11.2018 15:46, Alex Peshkoff via Firebird-devel wrote:
The user has a chance to avoid engine shutdown on signal caught using
fb_shutdown_callback() but that will be his choice.
There is a problem with older applications that know nothing about
fb_shutdown_calback() but still handle SIGINT
On 11/06/18 17:17, Adriano dos Santos Fernandes wrote:
On 06/11/2018 09:57, Dimitry Sibiryakov wrote:
06.11.2018 7:34, Alex Peshkoff via Firebird-devel wrote:
An idea was to have same behavior for remote and embedded
connections, please read doc/README.fb_shutdown, pay attention at
fb_shut_conf
On 06/11/2018 09:57, Dimitry Sibiryakov wrote:
> 06.11.2018 7:34, Alex Peshkoff via Firebird-devel wrote:
>> An idea was to have same behavior for remote and embedded
>> connections, please read doc/README.fb_shutdown, pay attention at
>> fb_shut_confirmation and a sample in the end.
>
> All this
06.11.2018 13:15, Alex Peshkoff via Firebird-devel wrote:
It can.
But if one does
kill `pidof firebird`
or presses ctrl-C when working with embedded library atexit is not called.
I see. But how about not calling fb_shutdown if old signal handler is not
SIG_DFL?
BTW, I cannot find in
On 11/06/18 14:57, Dimitry Sibiryakov wrote:
06.11.2018 7:34, Alex Peshkoff via Firebird-devel wrote:
An idea was to have same behavior for remote and embedded
connections, please read doc/README.fb_shutdown, pay attention at
fb_shut_confirmation and a sample in the end.
All this workaround
06.11.2018 7:34, Alex Peshkoff via Firebird-devel wrote:
An idea was to have same behavior for remote and embedded connections, please read
doc/README.fb_shutdown, pay attention at fb_shut_confirmation and a sample in the end.
All this workaround for workarounds just because engine cannot be
