Török Edwin wrote: [snip] > Have a look at bb #1139 for an example: lstat() failing for no apparent > reason.
The problems with lstat() are well known, and it doesn't fail randomly. But your point is that it affects clamav; I have never seen that particular failure, and I test clamscan/clamdscan/freshclam every time I install a new version (with the contents of the test directory). The bug #1139 mentions the same part I proposed to fix on checking, killing the daemon does not clear the socket, so I just added a remove before test; simple and besides in Cygwin we don't run the daemon directly, is controlled by cygrunsrv which sends the correct signal. > Try 'clamdscan ../test/clam.exe' vs. 'clamdscan clam.exe'. $ uname -a CYGWIN_NT-5.1 black 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin $ clamdscan -V ClamAV 0.94/8145/Wed Sep 3 01:00:57 2008 $ clamdscan clam.exe /home/rberber/Projects/clamav-0.94/test/clam.exe: ClamAV-Test-File FOUND ----------- SCAN SUMMARY ----------- Infected files: 1 Time: 0.109 sec (0 m 0 s) $ clamdscan ../test/clam.exe /home/rberber/Projects/clamav-0.94/test/../test/clam.exe: ClamAV-Test-File FOUND ----------- SCAN SUMMARY ----------- Infected files: 1 Time: 0.109 sec (0 m 0 s) What is supposed to not do? Or you meant run it continuously until it fails? -- René Berber _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
