summaryrefslogtreecommitdiffstats
path: root/catalog/systemd.catalog.in
diff options
context:
space:
mode:
authorAnita Zhang <anitzhang@gmail.com>2018-10-08 05:28:36 +0200
committerLennart Poettering <lennart@poettering.net>2018-10-18 09:56:20 +0200
commit90fc172e191f44979005a524521112f2bd1ff21b (patch)
treec7a62bfde5e0775425b209327d2be623a69ee8c5 /catalog/systemd.catalog.in
parentresolve: set IP_RECVERR (diff)
downloadsystemd-90fc172e191f44979005a524521112f2bd1ff21b.tar.xz
systemd-90fc172e191f44979005a524521112f2bd1ff21b.zip
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
Diffstat (limited to 'catalog/systemd.catalog.in')
-rw-r--r--catalog/systemd.catalog.in3
1 files changed, 2 insertions, 1 deletions
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