Nathan Brink wrote: > Sorry for double posting. > > Dennis Peterson wrote: >> Nathan Brink wrote: >> >>> Dennis Peterson wrote: >>> >>>> Pardon a bit of thread hijacking but... >>>> >>>> > >>>> Developers - could you unify the names of these sockets and invocation >>>> method? >>>> >>>> From clamd.conf: >>>> LocalSocket /var/run/clamav/clamd.sock >>>> TCPSocket 3310 >>>> TCPAddr 127.0.0.1 >>>> >>>> From clamav-milter.conf: >>>> ClamdSocket /var/run/clamav/clamd.sock (this is wrong, BTW) >>>> ClamdSocket tcp:127.0.0.1:3310 >>>> >>>> >>> I hope I have correctly interpreted your request; if I have, I like your >>> idea. clamd.conf should accept multiple Listening socket lines (maybe >>> with a Listen directive, which makes sense since other programs use this >>> terminology). This might look like: >>> #clamd.conf: >>> Listen unix:/var/run/clamav/clamd.sock >>> Listen tcp:localhost:3310 >>> Listen tcp:*:3333 >>> >>> #clamav-milter.conf: >>> ClamdSocket unix:/var/run/clamav/clamd.sock >>> ClamdSocket tcp:localhost:3310 >>> ClamdSocket tcp:remotehost:3333 >>> >> Not quite what I had in mind. The same socket has two different names >> depending >> on which conf file you read: >> >> Listen and ClamdSocket. Call it Listen or call it ClamdSocket, but not both. >> >> There are two different invocations: >> TCPSocket 3310 >> TCPAddr xx.xx.xx.xx >> >> and >> >> ClamdSocket tcp:host:socket >> >> Again, go with one or the other. For example, change clamd.conf to: >> ClamdSocket tcp:host:socket >> >> or change clamav-milter.conf to: >> Listen tcp:localhost:3310 >> Listen tcp:*:3333 >> > I'm afraid you or I have confused the meanings of ClamdSocket in > clamav-milter.conf and my proposed Listen keyword for clamd.conf.
My understanding is there is a connection made between clamav-milter and Sendmail/Postfix. That is a Unix or TCP socket and it has a logical name and a physical name. Another is made between clamav-milter and Clamd and again can be either a Unix or TCP socket. The logical name used by clamd can be the same as the logical name used by clamav-milter, no? I like the name ClamdSocket and suspect it could be used everywhere. The fact that the default socket special file name is clamd.sock rather speaks to this. I'm not suggesting the same name be used between the milter and the mta and the milter and the av daemon. If the question comes up what is the socket name in clamav-milter.conf and clamd.conf greping ClamdSocket on both files would return the same path. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
