Bug#884713: approx: systemd's approx.socket should be configured to not have any trigger limit
- To: 884713@bugs.debian.org
- Subject: Bug#884713: approx: systemd's approx.socket should be configured to not have any trigger limit
- From: Arnaud Rebillout <arnaudr@kali.org>
- Date: Mon, 22 Apr 2024 15:06:21 +0700
- Message-id: <[🔎] 557ff7b4-2d2f-4b4a-996f-b24ba900a639@kali.org>
- Reply-to: Arnaud Rebillout <arnaudr@kali.org>, 884713@bugs.debian.org
- In-reply-to: <151361164095.22721.17880888877293934341.reportbug@x260-buxy.home.ouaza.com>
- References: <151361164095.22721.17880888877293934341.reportbug@x260-buxy.home.ouaza.com> <151361164095.22721.17880888877293934341.reportbug@x260-buxy.home.ouaza.com> <151361164095.22721.17880888877293934341.reportbug@x260-buxy.home.ouaza.com>
On Mon, 18 Dec 2017 16:40:40 +0100 =?utf-8?q?Rapha=C3=ABl_Hertzog?=
<hertzog@debian.org> wrote:
> But IMO the default configuration should work even when you
make heavy use
> of the package repositories... so I would like to see this in
your default
> approx.socket. Or at least you should raise the limit to
something larger
> like a few thousands requests.
To add some more context: initially systemd defaulted to « 2500 activations per 5s », but then in v255
(commit from May 5, 2016), it changed to more
conservative defaults of « 200 activations per 2s » when Accept=yes. Cf.
https://github.com/systemd/systemd/commit/1f15ce28461ec54f85908efc063f99dc5a65b4ca.
--
Arnaud Rebillout / OffSec / Kali Linux Developer
Reply to: