On Mon, 07 Jun 2004 at 20:04:49 -0400, Mike Robinson wrote: > No, you just need to start clamd as a background daemon and then run > clamdscan in place of clamscan. As far as I know clamdscan is 100% > command line compatible with clamscan, so the only thing to worry about > is to make sure clamd stays up. > > Regards, > Mike >
Well, not exactly. Let me quote one of the Author's messages: ----------------------------------------------------------------------- From: Tomasz Kojm <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [Clamav-devel] clamdscan Message-Id: <[EMAIL PROTECTED]> Date: Wed, 2 Jun 2004 21:24:02 +0200 > Hi. > > As I take it clamdscan supports the exacts same options as clamscan, > right? No, it doesn't. It only accepts the same options as clamscan but strictly depends on clamav.conf. ----------------------------------------------------------------------- -- Tomasz Papszun SysAdm @ TP S.A. Lodz, Poland | And it's only [EMAIL PROTECTED] http://www.lodz.tpsa.pl/iso/ | ones and zeros. [EMAIL PROTECTED] http://www.ClamAV.net/ A GPL virus scanner ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
