On Fri, 2004-01-09 at 14:19, [EMAIL PROTECTED] wrote: > 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'...
Clamdscan (client) is the small client that connects to clamd (daemon/server) to request it to perform scans. Clamdscan needs clamd to be running in order to function. Clamscan is a standalone application. Cheers, Mike ------------------------------------------------------- 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
