Bookworm wrote:
That has its own flaws - namely, when it drops, it goes down hard for a long time.
Daemonizing it using svcscan/tcpserver is the only real way to keep it from going ga-ga on you.
Also, 18 megabytes isn't enough for the latest qmail-scanner with ClamAV. I've found that 30 is now the minimum.
Greg Kopp wrote:
I had the same problem.
I solved it by running clamd in daemon mode and running clamscan as a client in qmail-scanner. Originally I was running clamdscan directly from qmail-scanner (ala qmailrocks.org)
Greg
Micha Silver wrote:
Thanks for all the comments so far, but I'm still not having any luck. I've bumped the softlimit up to 30 MB, and that error still appears:
Jun 14 08:09:22 ns X-Qmail-Scanner-1.20: [ns.arava.co.il10871897614628938] clamscan: corrupt or unknown ClamAV scanner error or memory/resource/perms problem - exit status 2
Jun 14 08:09:28 ns X-Qmail-Scanner-1.20: [ns.arava.co.il10871897674628950] clamscan: corrupt or unknown ClamAV scanner error or memory/resource/perms problem - exit status 2
The qmail-scanner-queue.pl script is owned by qscand, and in a ps listing, each suidperl process is run by qscand:
[EMAIL PROTECTED] root]# ps aux | grep suidperl
qscand 13477 0.0 0.9 8240 4900 ? S 08:19 0:00 /usr/bin/suidperl -T /dev/fd/3//var/qmail/bin/qmail-scanner-queue.pl
qscand 18708 0.1 0.9 8268 4904 ? S 08:29 0:00 /usr/bin/suidperl -T /dev/fd/3//var/qmail/bin/qmail-scanner-queue.pl
qscand 20673 4.8 1.0 7456 5228 ? S 08:33 0:00 /usr/bin/suidperl -T /dev/fd/3//var/qmail/bin/qmail-scanner-queue.pl
qscand 20680 5.6 0.9 8820 4928 ? S 08:33 0:00 /usr/bin/suidperl -T /dev/fd/3//var/qmail/bin/qmail-scanner-queue.pl
qscand 20703 12.5 0.9 8144 4932 ? S 08:33 0:00 /usr/bin/suidperl -T /dev/fd/3//var/qmail/bin/qmail-scanner-queue.pl
qscand 20715 1.0 1.0 7456 5228 ? S 08:33 0:00 /usr/bin/suidperl -T /dev/fd/3//var/qmail/bin/qmail-scanner-queue.pl
qscand 20719 0.0 0.9 9084 4880 ? S 08:33 0:00 /usr/bin/suidperl -T /dev/fd/3//var/qmail/bin/qmail-scanner-queue.pl
As I mentioned before, clamd is up and running, and when I use the client clamdscan from a command line to scan a file, it works. However from the qmail-scanner script something causes it to bork. When I revert back to running clamscan within the qmail-scanner script it works OK (just uses a lot of memory and CPU time).
Any additional ideas ?
Thanks, Micha
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general