Red Hat Bugzilla – Bug 889795
engine: we use gzip -9 to zip files in engine instead of xz (vdsm already uses xz)
Last modified: 2016-06-12 19:15:54 EDT
Description of problem:
can we change ovirtlogrot.sh to use xz instead of gzip -9?
vdsm already uses xz so aside from the fact that xz compression is better, it will be nice if engine uses it too.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cd /var/log/ovirt-engine
2. ls -ltr
use gz to zip files
it would be nice to use xz
as you can see in /usr/share/ovirt-engine/scripts/ovirtlogrot.sh
we are using gzip -9
It'll reduce the compressed logs by 20-30%, which should be helpful for support log collection as well.
Need to check if it means we need to require xz in the spec file.
Merged change id: I2487d1a2505a43aa525b8d0d7af3557ce357d685
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.