Thierry Besancon wrote: > If you can create such a patch, why can't you apply it against a 0.93.1 > release and name the result 0.93.2 ? The bug is identified, isn't it ?
Then the people who aren't affected by it get yelled at by their freshclam daemon that they are out of date. I am just finishing getting everything to 0.93.1 and am not looking forward to having to do it again real soon just to fix something that does not affect me. > > The bug is quite severe. It stops my production server for one night. > As the bug only appears when new signatures are available, I had hard > time finding what may goes wrong. I subscribed to the mailing list > to look if other people were encountering the bug too. I tried to > search the archives that weren't not available because some html page > were zeroed. I started debugging the code too. So i can't accept > the easy answer "The problem you're facing could get fixed in 0.93.1 > if more people gave it a try". I gave it more than a try. I am still trying to figure out how you have FreeBSD/ClamAV set up to have this problem. I am running varios version of FreeBSD and have not seen this problem on any of them. If you are able to start debugging the code then patching it should be a trivial matter and I don't see why it is such a big deal. Steven _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
