summaryrefslogtreecommitdiff
path: root/man/journald.conf.xml
diff options
context:
space:
mode:
authorDavid Tardon <dtardon@redhat.com>2018-04-05 13:06:59 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2018-04-05 13:06:59 +0200
commit3de8ff5a69d0d30f099799ae661c0b8e337ae528 (patch)
treea9b53d012be29242140c6f38f13d8b9cc5d2e887 /man/journald.conf.xml
parent6064de2de8734401669b787b68ebbf858d452cec (diff)
downloadsystemd-3de8ff5a69d0d30f099799ae661c0b8e337ae528.tar.gz
journald: bump rate limits (#8660)
Apparently, it is quite common to hit a problem, where systemd-journald would drop messages because service is logging too fast.
Diffstat (limited to 'man/journald.conf.xml')
-rw-r--r--man/journald.conf.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index aaef49efd5..bd63a6a98c 100644
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -158,7 +158,7 @@
interval is over. A message about the number of dropped
messages is generated. This rate limiting is applied
per-service, so that two services which log do not interfere
- with each other's limits. Defaults to 1000 messages in 30s.
+ with each other's limits. Defaults to 10000 messages in 30s.
The time specification for
<varname>RateLimitIntervalSec=</varname> may be specified in the
following units: <literal>s</literal>, <literal>min</literal>,