Bug 14611

The typical installation of logwatch is arranged so that the local admin can change and extend logwatch to handle local site accommodations.  One change I have made for my systems here is a change to the disk usage module (zz-disk_space) that allows the admin to specify different threshholds for different file systems; currently the module is hardcoded so when disks fill to 90% or more, it issues warnings in the daily report.  I found that my own needs are different, so I customized it and proliferated it to all my own systems here... except for Mageia.

Another change I made is to display the actual percentage of disk space used, rather than the threshhold.  I believe this is more useful information overall.

BTW, there is a configuration file mod that has to be made, and probably I will need to address that before the maintainer can adopt my changes.  We don't want to break anyone's existing site.

I have filed these enhancement request at Sourceforge at https://sourceforge.net/p/logwatch/feature-requests/6/.

My request is to provide a way to make local site changes for logwatch as it is typically done on enterprise Linux, PCLinuxOS, Ubuntu, and others.  As it stands, there is no way in Mageia to make these changes without messing with the installed files.  Each time there is an update to Mageia logwatch, my local changes will be clobbered on my Mageia instance, which would be a minor nuisance.

I would like a workaround if a more permanent solution cannot be had at this time.

Thanks.