C. Bensend said: > >> Seriously though, why don't you just make a small script which >> contains the "settings" and use that every time? > > This is exactly what I do on my OpenBSD systems. I have a script > called 'reconfig' that simply does a ./configure with the options > that I prefer. > > A new version is released, I do a 'sh reconfig', 'gmake', 'gmake > install', and my new version is installed with exactly the same > options as the previous. > > Benny
Regarding the reconfig this is exactly my method as well. I take harsher steps to remove the old version before the install, and I also carefully review the new clamd.conf and freshclam.conf files to see if a new option has popped in since the last build. Or that the authors have decided to change the name of the conf file again. For my own peace of mind I always run make -n install just to be sure there are going to be no surprises. RCS is your friend when maintaining software such as this over time. RCS and cfengine together is heaven if you have more than a couple servers to keep up to date. dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
