On Sun, 2023-04-23 at 12:44 +0200, Damjan Georgievski wrote:

On Sun, 23 Apr 2023 at 07:53, Ralf Mardorf wrote:

...

assuming you can't get rid of the cause of messages flooding the log file, could you prevent writing with a filter? After all, only filtering when reading would not prevent the unnecessary growth of log files.

you didn't say which messages, but in systemd 253 there's a new per-unit option LogFilterPatterns=.

* A new LogFilterPatterns= option has been added for units. It may be used to specify accept/deny regular expressions for log messages generated by the unit, that shall be enforced by systemd-journald. Rejected messages are neither stored in the journal nor forwarded. This option may be used to suppress noisy or uninteresting messages from units.

Hi, thank you. There are actually no messages that spam my journal. I just want to know just in case. Regards, Ralf

On Sun, 23 Apr 2023 at 19:07, Luna Celeste wrote:

snip As with most (all?) solutions looking for a problem, this, too, is quite disconnected from reality.

Actually, I *have* this problem. But it is on C7. What it is, is a docker child that keeps sending logs entries, several times a second, up the chain to the host's system journal. The docker children are launched with docker-exec and because we are running a 3rd-party code we cannot modify the source without getting it re-certified and tested. Given the 6 figure number involved in those 2 steps, we are stuck with having to deal with the log entries as they come in the system journal. So this is not a solution looking for a problem. I hadn't spoken up before because it is on C7 and therefore on systemd219...