John Rudd wrote:
Dennis Peterson wrote:
Erez Epstein wrote:
Hello,
I see that about every month, there is new version,
what does one do when it has about 30 servers, that need to be updated?
is there an automatic way?
all servers have compiled versions of clamav.
I use Cfengine. All updates happen within 30 minutes regardless of how
many systems you have to update.
cfengine has a built in script for downloading only the most recent
clamav (and not re-downloading an existing one), building it, and
installing it?
Cfengine will do what ever you tell it to do. It is a framework but you
fill in the details. There are no turnkey solutions for solving
arbitrary data center needs - only tools. Cfengine is one such tool. One
could also write a script to do this, but Cfengine is already running
here so why not use it?
My usage is thus: Download and build the product from source. Verify it
works, examine the config files for new changes/requirements. Place the
built versions in the Cfengine repository. Update the Cfengine control
file to point to the new version. Update the configuration
documentation. Go back to doing what I was before this.
At this point I've not installed anything myself, but in a very short
time Cfengine will light off, see there is a new change in the master
configuration, and for every Cfengine client in the ClamAV class it will
put the files in place and restart clamav. This also works to distribute
internally any pattern file updates - especially for systems with no
connection to the Internet. This requires about 10 minutes of my time
over a period of about 25 minutes. Not demanding work at all.
It can do package and rpm based installs, too.
dp
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
