This is a guide to help you set up ClamAV on Ubuntu. First, you'll need to make sure you're getting packages from Universe. From the menu bar, go to System → Administration → Software Sources and check the "Community-maintained Open Source software (universe)" checkbox if it isn't already checked.
Now, open up a Terminal window and enter this command:
$ sudo apt-get install clamav
Before running your first scan, you'll want to update your anti-virus definitions:
$ sudo freshclam
Now you can finally run your first scan:
$ sudo clamscan -r -i / > mail name@example.com
This will run the on-demand virus scan (clamscan) on your computer's root directory; it will recurse through the entire filesystem (-r) and it will only output the names of infected files (-i). And when it's done running, it will send you an e-mail with the results of the scan. Alternately, you can redirect the output of the command to a text file. Just change mail name@example.com to clamscan.log. Or, if you'd rather have the output display to the screen, just remove the > and everything after it.
To set up a regular scan, you'll want to edit your /etc/crontab file:
$ sudo gedit /etc/crontab
Add these two lines to the end of the file and save the file:
0 12 * * * root freshclam
5 12 * * * root clamscan -r -i / > mail name@example.comThis runs every day at noon and updates the virus definitions before running the scan. You may want to make adjustments to the frequency or time of the scan, but this should give you a good starting point.
]]>Back during the Open Source CMS Conference (discussion on pingV.com) we attended a fundraiser/seminar hosted by Lullabot about Performance and Scalability. The presentation was really great. Some of it I knew already, some was new to me, but seeing it all presented together really helped solidify the concepts in my mind.
Shortly afterward we were engaged on a project that needed to really snap. The Make Earth Day Every Day project really needed their server to respond quickly. They also need it to handle large numbers of visitors - Earth Day was coming up! So, I put all my old and new performance tuning knowledge to work.
While most of these techniques apply to dedicated servers or VPS, some of the ideas are useful for shared hosts as well.
First, I used the Apache Benchmark tool to test out the servers and see how they would perform as a baseline. It's important to be methodical, do tests, make a small tweak, do more tests, and record the results along the way. You can't manage what you don't measure. With the default installation, the sites handled 5.5 requests per second. The Drupal cache wasn't enabled, so my first step was to do that. Immediately the performance went to 23 requests per second.
Using the vmstat diagnostic tools I learned about in the session I noticed that the CPUs on the web server were maxed out. So, I installed the APC opcode cache which drastically reduces the amount of processing and memory required for each page load. Without any further configuration requests per second went to 215.
Various other small tweaks (removing unnecessary Apache modules, and tweaks to the database configuration file) resulted in a gain of another 5 requests per second.
So, the final count is from 5 requests per second to over 220 requests per second. Given the nature of the site we expected users to spend a minute or more on each page which should allow for more than 13,000 simultaneous users.
There is much more valuable information in the output from the Apache Benchmark tool than just the requests per second, but it is an easy metric to use to help explain the magnitude of difference possible with some work in performance tuning.
I've talked mostly about the seminar at OSCMS2007 given by Lullabot and the slides are available online. But really there are lots of great articles on tuning from the Drupal community both in the Drupal.org Handbook and on various other sites like the 2bits.com book of Performance Tuning and Optimization for Large Sites.
Among all of these locations you can find lots of great information to help you tune your site for optimum performance.
]]>