Hi,
  I managed to fill my disk quite easily with a test zip:

$ mkfile -n 10g fileofdeath
$ zip -9 zipofdeeath fileofdeath

I thought an easy fix would be a softlimit -f 50000000 just before the
smtpd is started. This however stops qmail-scanner logging anything if
it's logs are over 50000000.
  Can some method of setting resource limits when the scanner or unzip is
executed be put in place? Some way of specifying:

/usr/local/bin/softlimit -f 50000000 /usr/local/bin/unzip ....

This file currently causes qmail scanner to seriously barf. I've held off
on attaching it to this message :)
  What can we do about this?
  I successfully caused the infamous 42.zip
http://www.fefe.de/antivirus/42.zip to not consume all the cpu with a
softlimit -t 120, but I'm not sure whether qmail scanner is actually just
retrying the file later?
  Cheers.

-- 
Mark Powell - UNIX System Administrator - The University of Salford
Information Services Division, Clifford Whitworth Building,
Salford University, Manchester, M5 4WT, UK.
Tel: +44 161 295 5936  Fax: +44 161 295 5888  www.pgp.com for PGP key


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Qmail-scanner-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general

Reply via email to