Centos 5.2, MS, perl ClamAV module
MailScanner at ecs.soton.ac.uk
Mon Dec 1 16:46:16 GMT 2008
On 1/12/08 14:02, David Lee wrote:
> On Sun, 30 Nov 2008, Scott Silva wrote:
>> on 11-27-2008 8:39 AM David Lee spake the following:
>>> Is the recommendation is that we no longer use the perl ClamAV module
>>> and instead use "clamd"?
>>> If so, then are all the pieces in place to ensure that the "clamd"
>>> module is automatically invoked? (The "chkconfig ..." and "service ...
>>> or equivalents?)
>> Since you are using CentOS 5, you can enable the rpmforge repo and
>> get spamassassin and clamav from yum.
>> The yum repo has a working clamd setup, and even Julian has
>> recommended this way with CentOS.
> Many thanks for that most ueful reply. Appreciated.
> For my particular instance, that sounds good; I've just done a quick
> test to verify it. (I'm hitting a couple of "selinux" oddities, but
> there's a possibility that they are because of local oddities here,
> not necessarily in the rpmforge packages.)
> For the general case (e.g. not CentOS; user installing SA/ClamAV
> package) might there still be a case for the SA/ClamAV to be able to
> install the "init.d" script (and other things) to provide a consistent
The reason I haven't done it in the past is that the init.d script has
to be totally different for every major Linux distro, let alone Solaris
and other Unices. So I would have to write half a dozen for it to be any
use. The current SA+ClamAV package is Unix-independent.
Julian Field MEng CITP CEng
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
PGP public key: http://www.jules.fm/julesfm.asc
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the MailScanner