Rob,

Thank you for your reply.

So to be clear, cron is calling a script (below).  I assume even though
cron is calling a script, rather than the individual commands in the
script, your same suggestion applies?  If so, would it be a matter of
adding 1>/dev/null to the end of each line?  I'm somewhat new to Linux,
so forgive my elementary queries.  Thank you.

clamscan  --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan /
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/_admin
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/bin
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/boot
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/etc
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/lib
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/mnt
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/opt
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/sbin
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/srv
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/tmp
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/usr
clamscan -r --move=/var/log/clam/infected -l /var/log/clam/dailyclamscan
/var


--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. If you have received this e-mail in error, or from 
someone who was not authorized to send it to you, do not disseminate, copy or 
otherwise use this e-mail or its attachments. Please notify the sender 
immediately if you have received this e-mail by mistake, and delete it from 
your system.



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

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
MacGregor
Sent: Monday, September 24, 2007 8:43 AM
To: ClamAV users ML
Subject: Re: [Clamav-users] Logging to /var/spool/mail/root

On 9/24/07, McGlynn, Sean (DOB) <[EMAIL PROTECTED]> wrote:
> Hello,
>
> The /var/spool/mail/root log files on our servers are logging every 
> file that clamav scans, causing the files to become huge.  I don't see

> what in our clamd.conf configuration files would be causing this.  Our

> configuration file follows - any help would be appreciated.

How are you calling clamav - if it's from cron then remember to redirect
the output or, as you're finding, root will get mailed with the output.

Otherwise - how about some detail?

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html

Reply via email to