Fwd: mx1 amavis-logwatch

[Michael Orlitzky]

Probably a stupid question, but is there any way I can avoid running the
backup scanner if the primary scanner timed out / got killed due to
$child_timeout?

I feel like clamscan is guaranteed to time out if the clamd scan did,
but I would still like it to kick in if I somehow break clamd (happened,
uh, once-ish, as far as anyone knows).


-------- Original Message --------

****** Detail (10)
*********************************************************************************

       2   *Warning: Virus scanner timeout
---------------------------------------------------------
       1      killing process [19591] running ClamAV-clamscan (reason:
on reading
       1      run_av (ClamAV-clamscan): collect_results - reading aborted

      10   Miscellaneous warnings
------------------------------------------------------------------
       3      Exception: incomplete data\n caught at
/usr/lib/perl5/vendor_perl/5.12.2/Mail/SpamA...
       3      Use of uninitialized value $xx in numeric ne (!=)
       1      ClamAV-clamd av-scanner FAILED: run_av error:
ask_daemon_internal: Exceeded allowed...
       1      ClamAV-clamscan av-scanner FAILED: run_av error: Exceeded
allowed time\n
       1      all primary virus scanners failed, considering backups
       1      process [19591] running ClamAV-clamscan is still alive,
using a bigger hammer