Replace xinetd support with the native listener [CORE5238] #5517
Assignees
Comments
Modified by: @dyemanovFix Version: 4.0 Alpha 1 [ 10731 ] assignee: Alexander Peshkov [ alexpeshkoff ] |
|
Commented by: @aafemt xinetd has much richer set of features than builtin listener. It can limit connection speed, number of connections from the same IP and so on. It would be nice to have a module that can be used with xinetd and transfer client sockets to main superserver process for further handling. |
|
Commented by: @AlexPeshkoff Such module can be written but I see no great use in it because xinetd is dying - it's not needed in case when systemd is used instead init. |
Modified by: @dyemanovFix Version: 4.0 Beta 1 [ 10750 ] Fix Version: 3.0.2 [ 10785 ] Fix Version: 4.0 Alpha 1 [ 10731 ] => |
Modified by: @dyemanovFix Version: 4.0 Alpha 1 [ 10731 ] Fix Version: 4.0 Beta 1 [ 10750 ] => Fix Version: 3.0.2 [ 10785 ] => |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @dyemanov
Votes: 1
Using the same native network listener (firebird process) on Classic would be the logical last step in unifying the architectures. It would simplify maintenance for us (no need to double install scripts) and production setup for end users (easy to detect running server, no need to tweak xinetd.conf re. max number of connections, etc.). Also, it would allow some new features requiring other-than-networking threads running inside the server.
Commits: e131cb3
The text was updated successfully, but these errors were encountered: