Description of problem: The glusterfs package installs an /etc/logrotate.d file that changes the global logrotate configuration that impacts all log files systemwide, not just glusterfs's. Version-Release number of selected component (if applicable): glusterfs-3.5.2-1.fc20 How reproducible: Always Steps to Reproduce: 1. Install Fedora without glusterfs or any other package that pulls in glusterfs, like libvirt/qemu, etc... 2. After a month, or so, observe that various log files are rotated out after four log rotation intervals 3. Install glusterfs, or any package that pulls in glusterfs Actual results: Suddenly, all system log files will now be rotated out after 52 log rotation intervals. /var/log won't be purged for at least a year, now. Expected results: Installing glusterfs should not affact any other packages' log rotation policies. Additional info: The "rotate 52" directive in /etc/logrotate.d/glusterfs-georep, and the other four directives in that file, take effect globally. They apply not only to the log files listed in this specific logrotate configuration file, but to all logrotate files. Those four directives need to be manually moved inside each individually config file entry, in this file.
Bug 1157457 has been filed to get the change in the upstream sources.
In fact, bug 1126802 (master branch) was already filed for this in the upstream project. This bug in the Fedora package will get fixed when Bug 1126801 has been fixed in upstream.
I see no reason to wait, especially since the fix is trivial.
(In reply to Sam Varshavchik from comment #3) > I see no reason to wait, especially since the fix is trivial. We're planning to include a fix in the next 3.5 stable update. Currently the Fedora package does not include its own logrotate configuration and just installs the files from upstream. It surely is cleaner to fix this upstream first.
Certainly it's cleaner to fix it upstream. But, instead of waiting for the upstream fix to percolate down, why not fix it in the package ahead of time, instead of waiting for the fixed version to get here. There are a couple of other global logrotate config directives in glusterfs's config file. I haven't analyzed their full impact; but it's a fair chance that they might end up having more negative impact than just the extended rotation interval, for some package that expects its log files to inherit the logrotate defaults.
*** This bug has been marked as a duplicate of bug 1143916 ***