The problem arises because we users are lazy and our lazy eyes can't differential between clamscan and clamdscan and clamd. The names are all too similar! Now freshclam is a reasonably different name and we don't get freshclam.conf confused with clamav.conf (even though they can be merged).
/etc/clamav.conf -> /etc/clamd.conf ?Perhaps, but this is not my decision.Because clamscan doesnt use clamav.conf!! Soooo many people dontPerhaps it should to avoid any confusion!
seem to realize this.
The whole purpose of clamscan is to be a command line config'ed scanner. Clamd is a file config'ed scanner. Where is the hardship in that? It's not rocket science. And it clearly states this in the documentation (if anybody reads it). If you want clamscan to run with specific settings each time, create a shell script to call it.
Exactly. I never said clamscan should use clamav.conf. I simply stated that since clamd/clamdscan (and optionally freshclam as well) are the only programs to use clamav.conf, perhaps it would avoid some confusion if it were to be called clamd.conf.
Jim
My point is that if we could make the names of the processes more distinguishable and match the conf files (if any) then we remove the chance of error. For example clamscan could be renamed to scanclam (with NO scanclam.conf), clamdscan renamed as daemonclam (with daemonclam.conf) or something like that.
Just my thoughts, but anyway the product is absolutely fantastic and streets ahead of the competition. Keep up the good work.
Bill
