> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Tom Walsh > Sent: Friday, January 09, 2004 1:44 PM > To: [EMAIL PROTECTED] > Subject: RE: [Clamav-users] pretty basic question - clamscan vs > clamdscan > > > > The difference between up and down is that one is up and one > > is down. Very profound, and not very helpful. Why bother > > answering if the answer in no way provides any explanation? > > Why bother responding only to chide the response for its lack of content > with more banter with similarly lacking substance?
I was attempting to make a point. I appolgize if my response was just another example of the exact thing i was bashing. > > To answer the question in a more detailed fashion... Clamd listens on a > socket. Clamdscan is a client interface for talking to that socket. > > Clamd's purpose is to avoid the performance hit of forking a new process > to scan a file or directory. > Thank you for a more detailed response. > Tom Walsh > > It is Friday... Can't we all just get along? > > Indeed. Its been too long a week.... Jim Maul Eastern Long Island Hospital
smime.p7s
Description: S/MIME cryptographic signature
