AW: Clamd and updates

[UxBoD]

Hi Jules,

Happy New Year!

I am using source and have set the path to /usr/local in virus.scanners.conf hence it actually working when running in daemon mode, but the lint doesn't actually pick it up.  If I remove esets and run a lint it works fine, so only if you have a combination it fails.

Regards,

--[ UxBoD ]--
// PGP Key: "curl -s https://www.splatnix.net/uxbod.asc | gpg --import"
// Fingerprint: C759 8F52 1D17 B3C5 5854  36BD 1FB1 B02F 5DB5 687B
// Keyserver: www.keyserver.net Key-ID: 0x5DB5687B
// Phone: +44 845 869 2749 SIP Phone: uxbod at sip.splatnix.net

----- Original Message -----
step 3.: "Julian Field" <MailScanner at ecs.soton.ac.uk>
To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
Sent: 31 December 2007 18:20:19 o'clock (GMT) Europe/London
Subject: Re: AW: Clamd and updates

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Ehle, Roland wrote:
>> Just noticed in my logfile :-
>>
>> Dec 30 12:30:02 mailhub update.virus.scanners: Found generic installed
>> Dec 30 12:30:02 mailhub update.virus.scanners: Running autoupdate for
>> generic
>> Dec 30 12:30:02 mailhub update.virus.scanners: Found esets installed
>> Dec 30 12:30:02 mailhub update.virus.scanners: Running autoupdate for
>> esets
>> Dec 30 12:30:02 mailhub esets-autoupdate[11205]: esets updated
>>
>> which shows that Clam is not being updated.  Now I guess that is
>> because no wrapper exists for ClamD.  I appreciate I can run freshclam
>> but how is this controlled through MS ?
>>
>> Also, when I run a lint against my MS installation I get the following
>> :-
>>
>> [root at mailhub bin]# ./MailScanner --lint
>> Trying to setlogsock(unix)
>> Checking version numbers...
>> Version number in MailScanner.conf (4.66.2) is correct.
>>
>> Your envelope_sender_header in spam.assassin.prefs.conf is correct.
>>
>> Checking for SpamAssassin errors (if you use it)...
>> SpamAssassin temp dir = /var/spool/MailScanner/spamassassin
>> SpamAssassin reported no errors.
>> MailScanner.conf says "Virus Scanners = esets clamd"
>> Found these virus scanners installed: esets, clamd
>> =======================================================================
>> ====
>> =======================================================================
>> ====
>> Virus Scanner test reports:
>> esets said "Found virus Eicar test file in eicar.com"
>>
>> If any of your virus scanners (esets,clamd)
>> are not listed there, you should check that they are installed
>> correctly
>> and that MailScanner is finding them correctly via its
>> virus.scanners.conf.
>>
>>
>> so eicar is being picked up via esets but not by clamd ????
>>
>> Any thoughts or ideas ? TIA
>>     
>
> Could you please check your /etc/MailScanner/virus.scanners.conf. All clam* entries there should have /usr/lib/MailScanner/clamav-wrapper  /usr.
>   
Unless you have installed it using my easy-to-install package rather 
than RPMs. If you have installed it from source or using my 
easy-to-install package of ClamAV+SpamAssassin, then you will need 
/usr/local and not /usr.

Jules

- -- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.7.0 (Build 1012)
Comment: Use Thunderbird's Enigmail add-on to verify this message
Charset: UTF-8

wj8DBQFHeTLlEfZZRxQVtlQRAlf0AKCSFpgc7yk9JqxdsXQx/uscPqJrawCfR06U
2NwhgeTXFcoMmXhZkQfmjpc=
=x+Qx
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner

Before posting, read http://wiki.mailscanner.info/posting

Support MailScanner development - buy the book off the website!

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.