Julio Maidanik said: > > I believe you are wrong: clamd socket, when specified in clamd.conf is > for > control only. > When a client, like clamdscan wants to pass data to clamd uses either a > temporary file or a socket (in case clamdscan input is stdin). > At least, that is what I conclude from the logs. > > Julio Maidanik
I don't use it with a Unix socket so could be wrong, but I did think one of the arguments you could pass to it was the location of a file to scan just as with a TCP socket. Don't know why this would be different based on socket type, but I'd still like the mentioned option. I'll test it out today on one of my dev boxen. dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
