The "for" loop may be more efficient on systems with large memory and multiple cores, to a point. Clamdscan will send the file to the running instance of clamd anyway, wont it? Won't clamd handle the threading and memory use and keep it manageable?
M^3 On Fri, Feb 15, 2008 at 2:40 PM, Tom Metro <[EMAIL PROTECTED]> wrote: > David E. Smith wrote: > > When clamdscan gets called, it gets called like this: > > C:\progra~1\clamav\clamdscan.exe -options c:\temp\foo\*.* > > > > Does anyone know of a wrapper program (or a ClamAV option) to work > > around the fact that I'm being forced to deal with wildcards? > > You can pretty easily do that on a Windows NT-era system with a batch > file. Run "help call" at a command prompt to get documentation on the > ways in which you can modify parameters passed to a batch file. So for > example: > > @echo off > C:\progra~1\clamav\clamdscan.exe %~p1 > > > will take the first argument (%1) passed to the batch file and modify it > to return just the path, which is then passed as the first argument to > the real command. > > clamdscan.exe should recursively scan the specified path. > > > If you really wanted to expand the wild card, that can be done too, with > additional effort. See "help for". It'd be something like: > > FOR %file IN (%1) DO C:\progra~1\clamav\clamdscan.exe %%file > > but far less efficient as it launches clamdscan.exe for each file. > > -Tom > > -- > Tom Metro > Venture Logic, Newton, MA, USA > "Enterprise solutions through open source." > Professional Profile: http://tmetro.venturelogic.com/ > _______________________________________________ > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32 > -- Michael M. Minor _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
