Hi there, On Wed, 13 May 2009 Kamens, Jonathan
> ... wanted to make clamscan a bit smarter ... > > * don't scan files more than 30 days old ... > * scan a rotating subset of those old files ... > * scan any files that were previously found to be infected ... > * don't scan files which have been explicitly suppressed > > ... I decided to go ahead and enhance clamscan ... > > I would be delighted to hear any feedback ... While these features might make a lot of sense, I can't help thinking that this isn't the 'Unix' (right:) way to go about implementing them. Would it not be better just to tell clamscan to accept the names of the files to scan on stdin (something like 'clamscan -f -' maybe?) and create a tool which can provide this list if one doesn't already exist? For most users, things like the standard 'find' or 'xargs' will be more than sufficient. You mentioned maintenance. IMO, what you're doing is asking for a maintenance headache. You mentioned changing the API. Please, for the sake of people that are using the package, already, don't do that unless there is (a) a VERY compelling reason and (b) NO other way. I'm already leaning towards abandoning ClamAV because of instability in the API. Sanesecurity is the only reason I continue to use it. -- 73, Ged. _______________________________________________ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
