Postfix Cyrus Web cyradm HOWTO

make && make install

11.1.3. Testing and configuring

To test the funtionality of clamav, you can run

clamscan

to get some results from

the testpatterns that are included in the clamav distribution run

clamscan  r  i

/usr/local/clamav 0.68

The output should look like this:

/usr/local/clamav 0.68/test/test1: ClamAV Test Signature FOUND

/usr/local/clamav 0.68/test/test1.bz2: ClamAV Test Signature FOUND

/usr/local/clamav 0.68/test/test2.zip: ClamAV Test Signature FOUND

/usr/local/clamav 0.68/test/test2.badext: ClamAV Test Signature FOUND

/usr/local/clamav 0.68/contrib/clamdwatch/clamdwatch.tar.gz: Eicar Test Signature FOUND

            SCAN SUMMARY            

Known viruses: 20482

Scanned directories: 47

Scanned files: 406

Infected files: 5

Data scanned: 5.48 MB

I/O buffer size: 131072 bytes

Time: 2.706 sec (0 m 2 s)

Next step is to setup the automated update of the virus database. This is a important

step, because the speed of virus spreading is fast and would pick up even further.

Create the needed logfiles

touch /var/log/clam update.log

chmod 600 /var/log/clam update.log

chown clamav /var/log/clam update.log

I suggest to update the signatures with a hourly cronjob. To edit the crontab issue

crontab  e

and add the following line, and replace the  x  with a random value

between 1 and 59. This is some kind of time based loadbalancing to ensure more

people can fetch the updated.

#x * * * *

/usr/local/bin/freshclam   quiet  l /var/log/clam update.log

To test if the update process is working, please issue the command

/usr/local/bin/freshclam  l /var/log/clam update.log

and have a look at the output.

The output should look similar to this:

ClamAV update process started at Tue Mar 23 19:58:11 2004

Reading CVD header (main.cvd): OK

42