Hmm, my script is a bit more complex as it: - unzip & untar - configure - make && make check - backs up the current clamav directory (who knows...) - backs up the configuration files - disable the clamav service (I'm running on Solaris) - make uninstall (from the previous build directory) - make install - mkdir, chown, chmod the service method and manifest subdirectories under the prefix directory (which is /opt/clamav here) - touches /opt/clamav/etc/clamd if needed - copies the manifest if needed - imports the manifest to create the service if needed - compares the old revision freshclam.conf.orig and freshclam.conf to reapply (patch) the same changes to the current freshclam.conf - does the same for clamd.conf - checks if my own signatures have not disappeared - enables the service and checks if it starts smoothly.
It's maybe overkill here and there but, for instance, I don't want to reconfigure manually clamav and freshclam from the default files, and I don't want to keep the old configuration files that may miss new settings. If you have any advise, please share ! Thank you Regards, Pierre On 13 Mar 2012 at 11:47, G.W. Haywood wrote: > [...] > What's wrong with a small shell script? > > #!/bin/bash > cd /tmp > tar xzvf /nfs_mount/clamav-x.xx.tgz > cd clamav-x.xx > ./configure --with-various-options > make > sudo make install > cd .. > rm -rf clamav-x.xx > > -- > > 73, > Ged. > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://www.clamav.net/support/ml > > _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
