On Mo, 21.08.23 11:07, Lennart Poettering (mzerqung@0pointer.de) wrote:
On Do, 17.08.23 08:25, Chris Adams (linux@cmadams.net) wrote:
Once upon a time, Lennart Poettering mzerqung@0pointer.de said:
Yes, and if this is not what you want, then disable the ratelimit. That's what I am saying?
It would be useful for systemd to have "cooldown periods" for things, similar to inetd and classic init, where misbehaving things (whether services or sockets) were paused for a time (configurable even) and then returned to service. AFAIK this is a flaw in general in systemd's limits; if something exceeds them, it takes manual intervention to reset them.
There's a TODO list item for that upstream already.
https://github.com/systemd/systemd/blob/main/TODO#L153
Definitely makes sense, and should be very easy to add, the underlying concepts are all implemented, it's just a matter of exposing this under new options.
I started working on this now:
https://github.com/systemd/systemd/pull/29159
Lennart
-- Lennart Poettering, Berlin