On 8 Mar 2007, at 01:29am, Tomasz Kojm wrote:
On Thu, 8 Mar 2007 01:18:19 +0000
Mark Allan <[EMAIL PROTECTED]> wrote:
When I cancel clamdscan by using ctrl-c or killall clamdscan the
clamdscan process dies but clamd continues to scan the file it's
currently on.
clamd will automatically detect that clamdscan disconnected and
terminate the
session while attempting to scan the next file in directory.
Thanks Tomasz, I've just tried that but it's still not doing the
right thing. Here's what I've done:
Started clamd
clamdscan /Users/mark/someReallyLargeFile.dmg
CTRL-C to cancel
At this point, clamd is still using lots of CPU cycles and when I
check to see which files are in use, it shows someReallyLargeFile.dmg
as still being open by clamd.
I then tried clamdscan /Users/mark/someTiny3KBfile.txt which scanned
and correctly returned no infection but someReallyLargeFile.dmg is
still open and in use by clamd which is still taking up some 60% CPU
time.
Thanks,
Mark
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
