I will submit one other possibility: I use --postmaster-only to send the
notices to a specific address, then have procmail pipe those to a script
that parses it and adds specific information to an SQL database --
(From To Subject Date/Time and what Virus).
This way my users' mailboxes aren't
I am trying to change the temporary directory for clamav but the change is
not working clamav is still writing to /tmp.
My clamd.conf
LogFile /var/log/clamav/clamd.log
LogFileMaxSize 5M
LogTime
TemporaryDirectory /var/clamavtmp/tmp
DatabaseDirectory /var/lib/clamav
TCPAddr 127.0.0.1
TCPSocket
TemporaryDirectory
* On 03/01/06 09:57 -0500, Brian McDonald wrote:
I am trying to change the temporary directory for clamav but the change is
not working clamav is still writing to /tmp.
My clamd.conf
LogFile /var/log/clamav/clamd.log
LogFileMaxSize 5M
LogTime
TemporaryDirectory /var
PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Daniel J
McDonald
Sent: Tuesday, January 03, 2006 10:11 AM
To: ClamAV users ML
Subject: RE: [Clamav-users] clamd.conf not recognizing
TemporaryDirectory
On Tue, 2006-01-03 at 10:06 -0500, Brian McDonald wrote:
You will have to explain what you mean by HUP
I restarted clamd using service clamd restart I also tried service clamd
stop and service clamd start but clamd is still writing to the /tmp
Are you sure you're changing the clamd.conf file that the installed
version of clamd is using? Try:
find / -name clamd.conf -print
You should only find
/attachment it was scanning? We had a
similar problem and I was able to identify a particular email attachment that
would send clamd (0.86.2) into just such a tailspin.
Brian
--
Brian McDonald
Never confuse being nice with being a tool.
___
http
All,
Around clamav version 0.84, I noticed clamav would crash or hang when
processing a particular zip file. One one system, clamd runs up to 99%
CPU and spins indefinitely (FreeBSD 4.8). On another (FreeBSD 4.10), it
crashes with a signal 4 (illegal instruction). I isolated the problem