The RHEL7 packages work correctly and
do not have any conflict with rsyslog.
The RHEL8 package is going to give me
some problems. Our syslog-ng configuration produces files
different than the default, so we have configured the logrotate
file appropriately. When the RPM update process runs the syslog-ng
package will be updated and because we do not have the rsyslog
package installed, the syslog-ng-logrotate package will be
installed.
This process will remove my custom
/etc/logrotate.d/syslog file and create a new default
/etc/logrotate.d/syslog-ng
This will break by logrotate
configuration on all systems that auto-update the RPM packages.
I think the correct approach would be
to move the /etc/logrotate.d/syslog file to
/etc/logrotate.d/syslog-ng when the syslog-ng-logrotate package is
installed for the first time.
Evan.
On 6/16/20 5:18 AM, Peter Czanik
(pczanik) wrote:
Hi,
There were multiple tickets, bug reports about logrotate
scripts in syslog-ng RPM packages for Fedora/RHEL.
- Installs the same logrotate script on RHEL/CentOS 7 as
rsyslog
- On RHEL/CentOS 8 and Fedora the logrotate script is
called syslog-ng and uses systemctl to reload syslog-ng
after rotation, just as the rsyslog variant. It is in a
separate subpackage, and installed only when rsyslog is
not on the system (for reasons check the RH bugzilla
ticket: in short it would not be used anyway due to
conflicts)
I tested it on Fedora 32 and CentOS 7, both with and without
rsyslog on the system. It worked fine for me, but any feedback
is appreciated.
If it is tested to work by someone else than me, I'll push the
changes both to the official EPEL package and to the syslog-ng
github repo.
Bye,
CzP
--
Evan Rempel