| Subject | OT: Firebird 4.0 xinetd Support on Linux Replaced |
|---|---|
| Author | Ismael L. Donis Garcia |
| Post date | 2017-08-24T15:36:51Z |
Sorry for the off topic, but I
have a doubt that maybe some of you can clarify
I was reading Firebird 4.0 Release Notes and I found the following note:
I was reading Firebird 4.0 Release Notes and I found the following note:
Tracker ticket CORE-5238
On Linux, Firebird 4 uses the same network listener process (Firebird) for all architectures. For Classic, the
main (listener) process starts up via init/systemd, binds to the 3050 port and spawns a worker firebird process
for every connection—similarly to what happens on Windows.
On Linux, Firebird 4 uses the same network listener process (Firebird) for all architectures. For Classic, the
main (listener) process starts up via init/systemd, binds to the 3050 port and spawns a worker firebird process
for every connection—similarly to what happens on Windows.
This has caused me the following doubt:
With this modification Firebird 4.0 will work on linux system that do not use systemd? Yes or no?
Best
Regards