> You need to test with an older bytecode.cvd, because the latest one has
> a workaround (0.96.3 loads it fast now because it doesn't load the new
> bytecodes at all).
>
> Attached bytecode.cvd version 103 for you to test.
> ClamAV 0.96.3 takes 2.5 minutes to load it on my box (probably much more
> on slower ones):
> $ time clamscan --quiet -dbytecode.cvd /dev/null
>
> real 2m32.461s
> user 2m32.287s
> sys 0m0.117s
>
> ClamAV 0.96.4 and 0.96.5 takes less than a second to load same CVD.
> $ time clamscan --quiet -dbytecode.cvd /dev/null
>
> real 0m0.591s
> user 0m0.500s
> sys 0m0.040s
Indeed. I've tested it like you suggested, with your bytecode.cvd, and I
did get the long startup times on both Maverick and Lucid, two separate
machines:
gimre@ximi:~/Desktop$ time clamscan --quiet -dbytecode.cvd /tmp
LibClamAV Warning:
***********************************************************
LibClamAV Warning: *** This version of the ClamAV engine is outdated.
***
LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/support/faq ***
LibClamAV Warning:
***********************************************************
real 3m20.331s
user 3m20.080s
sys 0m0.190s
After upgrading to -proposed, the problem got resolved:
gimre@ximi:~/Desktop$ time clamscan --quiet -dbytecode.cvd /tmp
On 12/21/2010 12:35 PM, Török Edwin wrote:
> You need to test with an older bytecode.cvd, because the latest one has
> a workaround (0.96.3 loads it fast now because it doesn't load the new
> bytecodes at all).
>
> Attached bytecode.cvd version 103 for you to test.
> ClamAV 0.96.3 takes 2.5 minutes to load it on my box (probably much more
> on slower ones):
> $ time clamscan --quiet -dbytecode.cvd /dev/null
>
> real 2m32.461s
> user 2m32.287s
> sys 0m0.117s
>
> ClamAV 0.96.4 and 0.96.5 takes less than a second to load same CVD.
> $ time clamscan --quiet -dbytecode.cvd /dev/null
>
> real 0m0.591s
> user 0m0.500s
> sys 0m0.040s
Indeed. I've tested it like you suggested, with your bytecode.cvd, and I
did get the long startup times on both Maverick and Lucid, two separate
machines:
gimre@ximi: ~/Desktop$ time clamscan --quiet -dbytecode.cvd /tmp ******* ******* ******* ******* ******* ******* ******* *** www.clamav. net/support/ faq *** ******* ******* ******* ******* ******* ******* ******* ***
LibClamAV Warning:
*******
LibClamAV Warning: *** This version of the ClamAV engine is outdated.
***
LibClamAV Warning: *** DON'T PANIC! Read
http://
LibClamAV Warning:
*******
real 3m20.331s
user 3m20.080s
sys 0m0.190s
After upgrading to -proposed, the problem got resolved:
gimre@ximi: ~/Desktop$ time clamscan --quiet -dbytecode.cvd /tmp
real 0m0.578s
user 0m0.550s
sys 0m0.020s
gimre@ximi: ~/Desktop$ apt-cache policy clamav dfsg-1ubuntu1. 10.10.1 dfsg-1ubuntu1. 10.10.1 dfsg-1ubuntu1. 10.10.1 0 ro.archive. ubuntu. com/ubuntu/ maverick- proposed/ main dpkg/status 96.3+dfsg- 2ubuntu1. 2 0 ro.archive. ubuntu. com/ubuntu/ maverick- updates/ main security. ubuntu. com/ubuntu/ maverick- security/ main 96.3+dfsg- 2ubuntu1 0 ro.archive. ubuntu. com/ubuntu/ maverick/main amd64
clamav:
Installed: 0.96.5+
Candidate: 0.96.5+
Version table:
*** 0.96.5+
500 http://
amd64 Packages
100 /var/lib/
0.
500 http://
amd64 Packages
500 http://
amd64 Packages
0.
500 http://
Packages
And on Lucid:
gimre@voy: ~/Desktop$ time clamscan --quiet -dbytecode.cvd /tmp
real 0m0.561s
user 0m0.540s
sys 0m0.020s
gimre@voy: ~/Desktop$ apt-cache policy clamav dfsg-1ubuntu1. 10.04.1 dfsg-1ubuntu1. 10.04.1 dfsg-1ubuntu1. 10.04.1 0 archive. ubuntu. com/ubuntu/ lucid-proposed/main Packages dpkg/status 96.3+dfsg- 2ubuntu1. 0.10.04. 2 0 ro.archive. ubuntu. com/ubuntu/ lucid-updates/main ro.archive. ubuntu. com/ubuntu/ lucid-security/main 96+dfsg- 2ubuntu1 0 ro.archive. ubuntu. com/ubuntu/ lucid/main Packages
clamav:
Installed: 0.96.5+
Candidate: 0.96.5+
Version table:
*** 0.96.5+
500 http://
100 /var/lib/
0.
500 http://
Packages
500 http://
Packages
0.
500 http://
Confirmed that -proposed packages fix the bug.
--
Imre Gergely
Yahoo!: gergelyimre | ICQ#: 101510959
MSN: gergely_imre | GoogleTalk: gergelyimre
gpg --keyserver subkeys.pgp.net --recv-keys 0x34525305