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 A rose by any other name may still be a rose, but config file contents are not so conveniently self-identifying. This identity creep can only produce confusion. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
