Comment 29 for bug 787864

Dear Dave!

Thanks for the reply, I got your point.

BUT

The problem is in confusing users (me at least :) )...

I test some folder using ClamTk in manual mode, then I get some result.
OK. If I trust to this result then I schedule ClamTk to perform it
regularly.
But it gives ANOTHER result! So I'm confused! I do believe, whatever
kind of possible results (only viruses / viruses + threads / whatever
else) but they MUST BE EQUAL using the same program!
>From developer's point of view I guess that the point is to use EXACTLY
THE SAME options using clamscan from GUI and from cron.

Another approach is to name different things in a different ways:
- use "GUI"-start of ClamTk to see only viruses and see results
immediately right on Clamtk' window
- use scheduler to launch ANOTHER possibility - standard clamscan's scan
that MIGHT give another result, then don't forget to check it regularly
in log-files
Such approach could add logic to what people see at least and, it would
be perfect, if new help system you started to write again could EXPLAIN
these differences.

Also, it would be perfect to have 2 more possibilities:
- to see some sign right on GUI window if any log-files obtained from
cron-clamscan report about viruses (or a message in system tray for such
a case) - I still believe that "install and forget" is a right approach
for average user, so it should be some reminder/notifier for case of
virus detected under background mode
- it would be beautiful would ClamTk allow different schedules per
different folders: mail, working folders, samba folders, downloads etc -
daily scan is OK; but linux packages, long archives, very long music and
video folders etc - less frequently (1/week, 1/months I think).
Speaking about me (for example): complete test of my laptop takes 2
hours, and my single chance is to restrict the scanning by certain areas
only - so I have to choose: either security or usefulness. And don't
forget that many of scheduled "long scans" on a laptop do not have
chances to be finalized due to mobile style of their owners.

Please don't think I press to you regarding this staff :) I just show
you "another" point of view and hope it might be useful for you.

However, I wish you to come to a quit simple and clear solution. And I
keep my promise to help with editing/translating of new help content
then.

Best regards,
Sergey Murzin

> Sergey,
>
> <quote>
> In general the same result like on SUSE, but what is strange:
> - despite here as well clamscan sees virus while clamtk not
> - it found only 1 virus among firefox files while could find those 4
> viruses that SUSE reported
> </quote>
>
> I think the differences you are spotting is because ClamTk will often avoid certain directories: mostly typical mail directories (like .thunderbird or .evolution) and sometimes even .mozilla directories. This is because parsing mail is a difficult thing to do. In Linux, mail files are typically just one file. So, if any part of it has a detected "virus" or something AND you quarantine or delete it, you just deleted the whole thing. That would be bad. I talk about this on the FAQ page:
> http://clamtk.sourceforge.net/faq.html#inbox
>
> respectfully
> dave
>