Hi there, On Sat, 4 Oct 2008 John Rudd wrote:
> ...what they REALLY ought to do is supply a tool which reads old > config files, and does something like a lint check. I believe there was a similar tool published by a user a while ago. Why not put this in bugzilla as suggested by Tomasz? (I haven't done it myself because I don't want to be accused of plagiarism. :) > clamavcfgcompiler -o oldconfigfile -n newconfigfile Many tools use -o as an output file option, so -1 to the naming of those options, but I agree the world isn't perfect. It might be better to use stdin and stdout. I'd suggest that since clam has to parse the config file anyway, it could do this itself, e.g. with a --test-config-file option, sending any errors to stderr/stdout, and exit with a non-zero error code if it does find errors in the config file. ..oOo.. FWIW I rarely upgrade ClamAV until at least a couple of weeks after a new release, precisely because it so often causes these troubles. Before anyone flames me, that's not a complaint. It's a statement of fact, possibly a suggestion to other ClamAV users, but nothing more. If the developers don't want to take it on board that's up to them. They'd no doubt point out that something like an anti-virus product is of necessity playing catch-up all the time, so it can never really be considered truly stable, at least until either the virus writers cease their evil trade or chip makers finally come up with something like immune hardware. (Or Microsoft collapses under its debt... :) -- 73, Ged. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
