# Logwatch on SLES12 **URL:** \ **Category:** SLES Configure-Administer\ **Created:** [April 5, 2019, 4:34pm UTC](https://forums.suse.com/t/logwatch-on-sles12/33785 "2019-04-05T16:34:11Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![System1](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@System1](https://forums.suse.com/u/System1)\ **Post date:** [April 5, 2019, 4:34pm UTC](https://forums.suse.com/t/logwatch-on-sles12/33785/1 "2019-04-05T16:34:11Z")
---
**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\ **Post date:** [April 5, 2019, 4:34pm UTC](https://forums.suse.com/t/logwatch-on-sles12/33785/2 "2019-04-05T16:34:11Z")
Upgrading from SLES11 to SLES12 changed the compression for rotated log files from bz2 to xz by default. This is fine, and I also know that how to change to default settings for logrotate. Still I am puzzled that the default configuration for logwatch was not adapted to this change. As shipped logwatch is not able to read archived log data and thus the --archives option is with not effect. How can I change the configuration for logwatch in order to make use of the xz utilities instead of bzip2? A corresponding setting is not present in the logwatch.conf. Günther ---
**Author:** ![Automatic\_Reply](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@Automatic\_Reply](https://forums.suse.com/u/Automatic_Reply)\ **Post date:** [April 10, 2019, 7:31am UTC](https://forums.suse.com/t/logwatch-on-sles12/33785/3 "2019-04-10T07:31:37Z")
Strap, It appears that in the past few days you have not received a response to your posting. That concerns us, and has triggered this automated reply. These forums are peer-to-peer, best effort, volunteer run and that if your issue is urgent or not getting a response, you might try one of the following options: - Visit [http://www.suse.com/support](http://www.suse.com/support) and search the knowledgebase and/or check all the other support options available. - Open a service request: [https://www.suse.com/support](https://www.suse.com/support) - You could also try posting your message again. Make sure it is posted in the correct newsgroup. ([http://forums.suse.com](http://forums.suse.com)) Be sure to read the forum FAQ about what to expect in the way of responses: [http://forums.suse.com/faq.php](http://forums.suse.com/faq.php) If this is a reply to a duplicate posting or otherwise posted in error, please ignore and accept our apologies and rest assured we will issue a stern reprimand to our posting bot… Good luck! Your SUSE Forums Team [http://forums.suse.com](http://forums.suse.com) ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [April 10, 2019, 6:23pm UTC](https://forums.suse.com/t/logwatch-on-sles12/33785/4 "2019-04-10T18:23:59Z")
Hi Günther, while I have not worked with logwatch configurations, a quick search on the net gave me the following patch for logwatch from 2017: [https://sourceforge.net/p/logwatch/discussion/1115928/thread/1fea3d5b/](https://sourceforge.net/p/logwatch/discussion/1115928/thread/1fea3d5b/) If that patch has not made it into the code yet, maybe sending a feature request to SUSE engineering (or the package maintainer) might be a good idea… Regards, J ---
**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\ **Post date:** [May 2, 2019, 12:58pm UTC](https://forums.suse.com/t/logwatch-on-sles12/33785/5 "2019-05-02T12:58:09Z")
On 4/10/19 5:24 PM, jmozdzen wrote:[color=blue] > while I have not worked with logwatch configurations, a quick search on > the net gave me the following patch for logwatch from 2017: > [https://sourceforge.net/p/logwatch/discussion/1115928/thread/1fea3d5b/](https://sourceforge.net/p/logwatch/discussion/1115928/thread/1fea3d5b/) > > If that patch has not made it into the code yet, maybe sending a feature > request to SUSE engineering (or the package maintainer) might be a good > idea…[/color] Thank you very much for the link. I might ask SUSE about it. Günther