From: Lennart Poettering Date: Fri, 6 Jan 2023 10:00:48 +0000 (+0100) Subject: man: document explicitly that LogRateLimit= has no effect on StandardOutput=file:… X-Git-Tag: v253-rc1~172 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=578033356d10f135a1fd146c929d68f41c658378;p=thirdparty%2Fsystemd.git man: document explicitly that LogRateLimit= has no effect on StandardOutput=file:… Fixes: #25951 --- diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index 78cede439c3..567a0fad321 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -2909,16 +2909,21 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX LogRateLimitIntervalSec= LogRateLimitBurst= - Configures the rate limiting that is applied to messages generated by this unit. If, in the - time interval defined by LogRateLimitIntervalSec=, more messages than specified in - LogRateLimitBurst= are logged by a service, all further messages within the interval are - dropped until the interval is over. A message about the number of dropped messages is generated. The time - specification for LogRateLimitIntervalSec= may be specified in the following units: "s", - "min", "h", "ms", "us" (see - systemd.time7 for details). - The default settings are set by RateLimitIntervalSec= and RateLimitBurst= - configured in journald.conf5. - + Configures the rate limiting that is applied to log messages generated by this + unit. If, in the time interval defined by LogRateLimitIntervalSec=, more messages + than specified in LogRateLimitBurst= are logged by a service, all further messages + within the interval are dropped until the interval is over. A message about the number of dropped + messages is generated. The time specification for LogRateLimitIntervalSec= may be + specified in the following units: "s", "min", "h", "ms", "us" (see + systemd.time7 for + details). The default settings are set by RateLimitIntervalSec= and + RateLimitBurst= configured in + journald.conf5. Note + that this only applies to log messages that are processed by the logging subsystem, i.e. by + systemd-journald.service. This means, if you connect a service's stderr directly + to a file via StandardOutput=file:… or a similar setting the rate limiting will + not be applied to messages written that way (but they will be enforced for messages generated via + syslog() or similar).