Enhanced system logging and kernel message trapping daemon
Go to file
Pavel Raiskup ad5200aa8c rsyslog.conf: first load default modules, then third-party config
When we installed file /etc/rsyslog.d/03-ratelimits.conf:

    $IMJournalStateFile imjournal.state
    $IMJournalPersistStateInterval 1000
    $IMJournalRatelimitInterval 1
    $IMJournalRatelimitBurst 10000

rsyslog failed:

    invalid or yet-unknown config file command 'IMJournalStateFile' - have you forgotten to load a module? [v8.2010.0 try https://www.rsyslog.com/e/3003 ]
    invalid or yet-unknown config file command 'IMJournalPersistStateInterval' - have you forgotten to load a module? [v8.2010.0 try https://www.rsyslog.com/e/3003 ]
    invalid or yet-unknown config file command 'IMJournalRatelimitInterval' - have you forgotten to load a module? [v8.2010.0 try https://www.rsyslog.com/e/3003 ]
    invalid or yet-unknown config file command 'IMJournalRatelimitBurst' - have you forgotten to load a module? [v8.2010.0 try https://www.rsyslog.com/e/3003 ]

That's because imjournal was loaded later than that config file.  If
module was explicitly loaded via '$ModLoad imjournal' in our third-party
file, we got a different error:

    module 'imjournal' already in this config, cannot be added  [v8.2010.0 try https://www.rsyslog.com/e/2221 ]

When the config file is reordered like this, no errors are shown.

Resolves: rhbz#1985202
2021-07-27 09:38:24 +02:00
.gitignore rebase to upstream version 8.2102.0 2021-03-15 09:09:27 +01:00
rsyslog.conf rsyslog.conf: first load default modules, then third-party config 2021-07-27 09:38:24 +02:00
rsyslog.log Use systemctl for sending SIGHUP to the service 2015-06-29 11:49:24 +02:00
rsyslog.service rebase to upstream version 8.2008.0 2020-09-17 12:09:47 +02:00
rsyslog.spec rsyslog.conf: first load default modules, then third-party config 2021-07-27 09:38:24 +02:00
rsyslog.sysconfig Rebase to an upstream snapshot 2013-06-04 21:06:48 +02:00
sources rebase to upstream version 8.2102.0 2021-03-15 09:09:27 +01:00