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
According to https://fedoraproject.org/wiki/Packaging:Scriptlets:
If a package is suitable for installation without systemd (in a
container image, for example) and does not require any of the
systemd mechanisms such as tmpfiles.d, then the systemd_ordering macro
MAY be used instead of the systemd_requires macro.
That is exactly the case we want to address for container images
when installing packages in it.
Resolves: rhbz#1668688
Related-Bug: #1804822
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
