thanks. i suspect my invocation needs to be different - when i switch from clamscan to clamdscan, messages are processed - for example - rather than taking 10 seconds, 20 seconds, etc with clamscan, they claim 'ok' in .1 seconds, .7 seconds, etc - which doesn't seem possible.
following up on my own message here - the name clamdscan implies a daemon unto itself, that's why it seems - odd - if clamdscan is to be invoked the same as clamscan. If clamdscan is to run persistently, i'd expect it to be started up once, a la clamd. but perhaps i'm misinterpreting the name - perhaps it doesn't mean 'clam scanning daemon' but rather 'clamd-associated scanning process'...
Paul Theodoropoulos http://www.anastrophe.com
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
