[Clamav-users] freshclam virus list out of date
it seems that with freshclam -v command I get virus list out of date ; this is output freshclam : azerty:~$freshclam -v Current working dir is /usr/local/share/clamav max retries==3 ClamAV update process started at Fri Sep 26 10:43:42 2008 Using IPv6 aware code Quering current.cvd.clamav.net WARNING:Can't query current.cvd.clamav.net WARNING:Invalid DNS reply. Falling back to HTTP mode If-Modified-Since:Thu,25 Sep 2008 16:03:11 GMT Reading CVDheader(main.cvd):Trying host database.clamav.net(193.52.101.131) ... Connected to database.clamav.net(IP:193.52.101.131). Trying to retrieve CVD header of http://database.clamav.net/main.cvd OK (IMS) main.cvd is up to date (version:47,sigs:312304,f-level:31,builder:sven) Assuming modification time in the past If-Modified-Since:Mon,27 Dec 2004 03:52:10 GMT Reading CVD header(daily.cvd):Connected to database.clamav.net(IP:193.52.101.131) Trying to retrieve CVD header of http://database.clamav.net/daily.cvd OK daily.cld is up to date (version:8342, sigs:3,f-level:35,builder:ccordes) ## and output clamscan -r -i / >/in_a file --- SCAN SUMMARY --- Known viruses: 347519 ( there's now Total number of signatures: 434939 ) Engine version: 0.94 Scanned directories: 85 Scanned files: 368 Infected files: 0 Data scanned: 155.19 MB Time: 23.456 sec (0 m 23 s) About freshclam.conf only example is comment as usually i do Could someone help me ? Regards Roger ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[Clamav-users] freshclam virus list out of date
What version of freshclam do you have? On Sat, 2008-09-27 at 08:51 +, Roger MARTINEZ wrote: > it seems that with freshclam -v command I get virus list out of date ; > > this is output freshclam : > azerty:~$freshclam -v > Current working dir is /usr/local/share/clamav max retries==3 > ClamAV update process started at Fri Sep 26 10:43:42 2008 > Using IPv6 aware code > Quering current.cvd.clamav.net > WARNING:Can't query current.cvd.clamav.net > WARNING:Invalid DNS reply. Falling back to HTTP mode > If-Modified-Since:Thu,25 Sep 2008 16:03:11 GMT > Reading CVDheader(main.cvd):Trying host database.clamav.net(193.52.101.131) > ... > Connected to database.clamav.net(IP:193.52.101.131). > Trying to retrieve CVD header of http://database.clamav.net/main.cvd OK (IMS) > main.cvd is up to date (version:47,sigs:312304,f-level:31,builder:sven) > Assuming modification time in the past > If-Modified-Since:Mon,27 Dec 2004 03:52:10 GMT > Reading CVD header(daily.cvd):Connected to > database.clamav.net(IP:193.52.101.131) > Trying to retrieve CVD header of http://database.clamav.net/daily.cvd OK > daily.cld is up to date (version:8342, sigs:3,f-level:35,builder:ccordes) > > ## > > and output clamscan -r -i / >/in_a file > > --- SCAN SUMMARY --- > Known viruses: 347519 ( there's now Total number of signatures: 434939 > ) > Engine version: 0.94 > Scanned directories: 85 > Scanned files: 368 > Infected files: 0 > Data scanned: 155.19 MB > Time: 23.456 sec (0 m 23 s) > > About freshclam.conf only example is comment as usually i do > > Could someone help me ? > > Regards > > Roger freshclam version is freshclam -V ClamAV 0.94/8346/Sat Sep 27 09:08:52 2008 regards Roger ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
[Clamav-users] clamscan error and requirements
After a clamscan command ,i obtain this output with clamav0.88.1 source release LibClamAV Error: fileblobAddData: Can't write 76 bytes to temporary file textpart: No space left on device LibClamAV Error: fileblobAddData: Can't write 76 bytes to temporary file textpart: No space left on device LibClamAV Error: fileblobAddData: Can't write 76 bytes to temporary file textpart: No space left on device LibClamAV Error: fileblobAddData: Can't write 76 bytes to temporary file textpart: No space left on device LibClamAV Error: fileblobAddData: Can't write 76 bytes to temporary file textpart: No space left on device LibClamAV Error: fileblobAddData: Can't write 76 bytes to temporary file textpart: No space left on device LibClamAV Error: fileblobAddData: Can't write 76 bytes to temporary file textpart: No space left on device LibClamAV Error: fileblobAddData: Can't write 76 bytes to temporary file textpart: No space left on device LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries LibClamAV Warning: Multipart MIME message contains no boundaries # and the resultt is : --- SCAN SUMMARY --- Known viruses: 51002 Engine version: 0.88.1 Scanned directories: 75 Scanned files: 404 Infected files: 0 Data scanned: 495.85 MB Time: 394.753 sec (6 m 34 s) hard drive partitionning is : Sys. de fich.1K-blocs Occupé Disponible Capacité Monté sur /dev/hda8 964500287920627584 32% / tmpfs 517496 0517496 0% /dev/shm /dev/hda1 7164956 2476116 4688840 35% /mnt/windows /dev/hda9 20192676 16708844 3073536 85% /usr /dev/hda1020192676 7731048 12051332 40% /usr/local /dev/hda1124636408 15032260 8853272 63% /home /dev/hda13 1057812797020217740 79% /bak /dev/hda569973 29388 36972 45% /boot /dev/hda6 1478668608664809924 43% /var /dev/hda7 280005 8255257294 4% /tmp After a clamscan /tmp seems to fill a lot ; however it can give an answer , command is clamscan -r --infected /home/roger/.mozilla >/home/roger/Infection/Analyse_160406 is there a minimal size of /tmp to start clamav , in 0.88 source release there is not problem with the same command ( and same verification file ) Can anyone help me ? Best regards Roger Martinez Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34 /mn) ; tél : 08 92 68 13 50 (0,34/mn) ___ http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] clamscan error and requirements
> > > roger martinez escreveu: > > LibClamAV Error: fileblobAddData: Can't write 76 bytes to > > temporary file textpart: No space left on device > > LibClamAV Error: fileblobAddData: Can't write 76 bytes to > > temporary file textpart: No space left on device > > LibClamAV Error: fileblobAddData: Can't write 76 bytes to > > temporary file textpart: No space left on device > > LibClamAV Error: fileblobAddData: Can't write 76 bytes to > > temporary file textpart: No space left on device > > LibClamAV Error: fileblobAddData: Can't write 76 bytes to > > temporary file textpart: No space left on device > > LibClamAV Error: fileblobAddData: Can't write 76 bytes to > > temporary file textpart: No space left on device > > LibClamAV Error: fileblobAddData: Can't write 76 bytes to > > temporary file textpart: No space left on device > > LibClamAV Error: fileblobAddData: Can't write 76 bytes to > > temporary file textpart: No space left on device > > > > No Space left on device usually means 'out of space' !! There's no > magic or hidden message on that, there's no space for doing something > the process was supposed to do. > > > After a clamscan /tmp seems to fill a lot ; however it can > > give an answer , > > command is clamscan -r --infected /home/roger/.mozilla > > > >> /home/roger/Infection/Analyse_160406 > >> > > > > hard drive partitionning is : > > > > Sys. de fich.1K-blocs Occupé Disponible Capacité > > Monté sur > > /dev/hda8 964500287920627584 32% / > > tmpfs 517496 0517496 0% /dev/shm > > /dev/hda1 7164956 2476116 4688840 35% > > /mnt/windows > > /dev/hda9 20192676 16708844 3073536 85% /usr > > /dev/hda1020192676 7731048 12051332 40% /usr/local > > /dev/hda1124636408 15032260 8853272 63% /home > > /dev/hda13 1057812797020217740 79% /bak > > /dev/hda569973 29388 36972 45% /boot > > /dev/hda6 1478668608664809924 43% /var > > /dev/hda7 280005 8255257294 4% /tmp > > is there a minimal size of /tmp to start clamav , in 0.88 > > source release there is not problem with the same command ( > > and same verification file ) > > > > > > Your /tmp is small, that's a fact. I dont know if clamav needs a > 'minimal space of /tmp to start', but i think the answer is NO. The > minimal space needed depends on the files clamav will have to scan. I > would worry about compressed files, maybe clamav decompress and writes > on /tmp to scan the decompressed ones. > > Please try changing TemporaryDirectory to something different from > /tmp in clamd.conf. Gives TemporaryDirectory a path will more space > available and try it. I think you should have a /var/tmp in your linux. > Try it ! > > > -- > > > Atenciosamente / Sincerily, > Leonardo Rodrigues > Solutti Tecnologia > http://www.solutti.com.br > > Minha armadilha de SPAM, NÃO mandem email > [EMAIL PROTECTED] > My SPAMTRAP, do not email it > > > > > ___ > http://lurker.clamav.net/list/clamav-users.html > Good afternoon Leonardo i saw your message and i tried So , no succes ! i just modify clamd.conf in TemporaryDirectory uncomment line and put /usr/local/tmp clamav continue to work with /tmp i don't know what to do Best regards Roger Martinez Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34 /mn) ; tél : 08 92 68 13 50 (0,34/mn) ___ http://lurker.clamav.net/list/clamav-users.html
Re: [Clamav-users] clamscan error and requirements
> > i saw your message and i tried > > So , no succes ! > > > > i just modify clamd.conf in TemporaryDirectory > > uncomment line and put /usr/local/tmp > > clamav continue to work with /tmp > > i don't know what to do > > > > Best regards > > > > Roger Martinez > > Did you kill clamd and restart it? > > dp > ___ > http://lurker.clamav.net/list/clamav-users.html > clamscan command still follow to work with /tmp If i modify the 2 clamd.conf (I have sources ) to /usr/local/tmp , it's the same the error is the same as highly. can somebody try to change TemporaryDirectory /tmp to /usr/local/tmp and before shuttingdown pc control with ls -a new tmp diectory please About clamd of course it's not in use then nothing to kill best regards Roger Martinez Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34 /mn) ; tél : 08 92 68 13 50 (0,34/mn) ___ http://lurker.clamav.net/list/clamav-users.html
