[pmg-devel] [PATCH pmg-api] Drop sa-awl output from pmg-system-report

Stoiko Ivanov s.ivanov at proxmox.com
Tue May 28 12:32:57 CEST 2019


After gathering some initial experience with `pmg-system-report` it seems
that the output of `sa-awl` is not too helpful in narrowing down problems.

Additionally the output tends to be quite large (multiple MiB) on larger/
longer-running installations, leading to timeouts or problems when sending
the report to the support.

Should the AWL checks skew the SA-results in a negative way this already shows
in the logs (which log the score for each rule).

Signed-off-by: Stoiko Ivanov <s.ivanov at proxmox.com>
---
 PMG/Report.pm | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/PMG/Report.pm b/PMG/Report.pm
index 0472b6a..0fe742b 100644
--- a/PMG/Report.pm
+++ b/PMG/Report.pm
@@ -9,8 +9,6 @@ $ENV{'PATH'} = '/sbin:/bin:/usr/sbin:/usr/bin';
 
 my $cmd_timeout = 10; # generous timeout
 
-my $sa_awl_db = '/root/.spamassassin/auto-whitelist';
-
 # NOTE: always add new sections to the report_order array!
 my $report_def = {
     general => {
@@ -46,7 +44,6 @@ my $report_def = {
 	sub { dir2text('/etc/pmg/','(?:domains|mynetworks|tls_policy|transport)' ) },
 	sub { dir2text('/etc/pmg/templates/', '[^.].*' ) },
 	'pmgdb dump',
-	"[ -f '$sa_awl_db' ] && sa-awl '$sa_awl_db'",
     ],
 };
 
-- 
2.11.0




More information about the pmg-devel mailing list