TCP hardlimits (!336) · Merge requests · Knot projects / Knot DNS · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.

Jan Včelák requested to merge master_tcp_hardlimits into master Feb 09, 2015

Several bugs fixed:

TCP client count can be limited by the config variable max_tcp_clients in system (so there are free descriptors for autonomous operation)
Aggressive limits when client connects, but doesn't start sending data in time
Throttling doesn't affect activity other then accept()
Possible resource leak on tcp_sweep
Bad logic (started reading from socket before checking for error activity first)
Bad logic (could close master socket on fd exhaustion)

fixes #326 (closed)