From 90fc172e191f44979005a524521112f2bd1ff21b Mon Sep 17 00:00:00 2001 From: Anita Zhang Date: Sun, 7 Oct 2018 20:28:36 -0700 Subject: core: implement per unit journal rate limiting Add LogRateLimitIntervalSec= and LogRateLimitBurst= options for services. If provided, these values get passed to the journald client context, and those values are used in the rate limiting function in the journal over the the journald.conf values. Part of #10230 --- catalog/systemd.catalog.in | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'catalog') diff --git a/catalog/systemd.catalog.in b/catalog/systemd.catalog.in index 22d5d5d50c..49a45890f6 100644 --- a/catalog/systemd.catalog.in +++ b/catalog/systemd.catalog.in @@ -52,7 +52,8 @@ dropped, other services' messages are unaffected. The limits controlling when messages are dropped may be configured with RateLimitIntervalSec= and RateLimitBurst= in -/etc/systemd/journald.conf. See journald.conf(5) for details. +/etc/systemd/journald.conf or LogRateLimitIntervalSec= and LogRateLimitBurst= +in the unit file. See journald.conf(5) and systemd.exec(5) for details. -- e9bf28e6e834481bb6f48f548ad13606 Subject: Journal messages have been missed -- cgit v1.2.1