Resolves: RHEL-70110
Fix $ActionQueueDiscardMark default value to 80% queue size
Resolves: RHEL-41153
Fix segfault when $ControlCharacterEscapePrefix is set
Resolves: RHEL-35823
Fix segfault due to processing malform queue message
Resolves: RHEL-33451
Fix crash on startup when an invalid function is specified
Resolves: RHEL-59893
Startup rsyslog service after network-online.target
Resolves: RHEL-39284
Harden service file
Resolves: RHEL-39237
imjournal: PID nummber is retrieved from the journal by default
Resolves: RHEL-39413
In the past, the logrotate script was part of the base package, but
it has been moved to a separate package to reduce base package
dependencies. It turned out to be a bad idea, because in some cases
the logrotate subpackage was not installed and the logrotate config
was missing. This turned off rotation of important logs, thus some logs
could grow into extremely large files .
It appears that some people are finding use for this rsyslog module, and
it doesn't add any more build-dependencies for rsyslog.
Add it as a bcond to make a more minimal rsyslog possible, as well as
keeping the pattern of having all of these as options.
Fixes: https://github.com/amazonlinux/amazon-linux-2023/issues/122
The way qpid-proton's sources are specified, any automated build outside of RH infrastructure will fail as it won't know where to get them from. This makes the source a proper URL.
In 5f74814 (Use systemctl for sending SIGHUP to the service,
2015-06-29), a direct call to `kill` was replaced with `systemctl kill`.
This can be simplified using `systemctl reload` instead. Doing so also
resolves an issue when `POSIXLY_CORRECT` is set (rhbz#2124488).
Move to bcond: rdkafka, relp, mysql, pgsql, gssapi, gnutls, udpspoof, omamqp1
Move to bcond: clickhouse, imdocker, improg
The idea was initiated by trawets at PR32
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
