Hi,
Eric Rostetter wrote:
> Quoting Colin Alston <karnaugh@karnaugh.za.net>:
>
>> ClamAV has been continuously and repetitively adjusting configuration
>> options in such a way that breaks anything which is automatically
>> upgraded just stops working.
Why not have a scan for obsolete or bad parameter usage, if found, then copy
the current config to a special backup file and then automatically edit the
current config with comment lines and comment parameters such as follows:
Before:
PARAM1=xxxx
PARAM2=yyyy
PARAM3=zzzz
After:
PARAM1=xxxx
#PARM2 has been deprecated in version 0.x.x
# - please see URL here for further information
#PARAM2=yyyy
PARAM3=zzzz
Now you have a documented and updated configuration file with references to
check out if you need further information.
Perhaps with the above, you don't need a special backup file, but it would
make sense to create a dated one though with code like this:
cp -p $OLD_CONFIG_FILE $OLD_CONFIG_FILE.`date +%Y%m%d`.a
NB: the '-p' option for cp so that the file/date time of the original file
doesn't change. The trailing '.a' being used to denote first version for
this date.
Then process the orginal file with the comments.
Kind Regards
AndrewM
Andrew McGlashan
Broadband Solutions now including VoIP
Current Land Line No: 03 9912 0504
Mobile: 04 2574 1827 Fax: 03 9012 2178
National No: 1300 85 3804
Affinity Vision Australia Pty Ltd
http://www.affinityvision.com.au
http://adsl2choice.net.au
In Case of Emergency --
http://www.affinityvision.com.au/ice.html
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
(text/plain)