Hi there, On Sat, 19 Oct 2019, Ian via clamav-users wrote:
This line of questioning is completely off-topic and unhelpful.
If you say so.
Are you going to address why 'clamscan --tempdir /tmp /tmp' doesn't produce the same behavior, that 'clamdscan /tmp' does?
The clamd daemon has a man page which you should read. It is, er, a daemon, which, when you start it, loads some databases and then sits and waits for something to send it things to scan against the loaded databases. It can do a few other things too, like reload databases and report statistics, but basically it sits and waits for commands and data. The clamd daemon has its own configuration file. It is usually called 'clamd.conf'. This has its own man page, which you should also read. The clamdscan tool has a man page which you should read. Its use is generally to send stuff to the clamd daemon for scanning. The clamscan tool has a man page which you should read - it is about three times as long as the man page for clamdscan. This is a stand- alone command-line tool and it does *not* use the clamd daemon to do the scanning (and the configuration file for the clamd daemon has no effect whatsoever on clamscan; you don't even need to have the clamd daemon installed to be able to use clamscan). Note carefully the differences between clamscan and clamdscan, which, although they have names differing only by one letter, behave in very different ways. Of course if you'd read the documentation as I've asked you to, you'd know all that already and you wouldn't be asking the question. -- 73, Ged. _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
