Re: [webmin-l] Webmin module for Clamav?

[Richard C. <rch...@aa...>]

Thanks Steve

I checked the permissions of /var/log/calmav and it is owned by clamav 
and the owner has write permission.
Indeed - the log file freshclam.log exists and has some reasonably 
sensible stuff in it. However - there is no clam.log file there - and 
the error I get from the webmin module is:

*WARNING: *Please fill in the location of the ClamAV log file in the 
module's configuration.

I have of course checked the log file entry in the module config and it 
is set  to:

/var/log/clamav/clamav.log

which looks correct to me.

My intention is to use clamav to scan incoming mail - probably using 
procmail - so I probably do need the milter.
I am not sure what the basic "clamav' module includes - and whether I 
need it - but it is there anyway.

If you have any other suggestions - they would be appreciated.

Richard.





steve wrote:
> Clamav 0.94 -> 0.95 is a fairly major change, so an old admin interface
> *may* not work. However, at a system level, the log file location must
> exist, and must also be writable by the clamav user ( which is usually -
> surprisingly! - clamav ). It may well be the second part that's tripping
> you up. I usually create a /var/log/clamav directory, and chown
> clamav:clamav /var/log/clamav. This usually does it.
>
> You should only need the clamav-milter module if you're interfacing to
> sendmail or procmail. In fact, if all you're doing is providing a
> socket/port for applications to use, then you only really need clamd.
>
> Sorry I've not played with the module.
>
> Steve
>
> On Thu, 2009-06-11 at 13:16 +0800, Richard Chapman wrote:
>   
>> Thanks Marcos
>>
>> I installed that package - and the rpmfoege clamav packages:
>> clamv, clamnav-db, calamd, clamav-milter from dag repository on my 
>> centos 5 system.
>> When I go to the webmin clamav page - I now get the error:
>>
>> ------------------------------------------------------------------------
>>
>> *WARNING: *Please fill in the location of the ClamAV log file in the 
>> module's configuration.
>>
>> ------------------------------------------------------------------------
>>
>> I have checked the module config - and both log file paths calmav and 
>> freshclam seem to be filled in and reasonable.
>>
>> Any ideas how I get past this warning?
>>
>> Thanks
>>
>> Richard.
>>