Nico, > >Now my question: why is clamd listening on a TCP port (only one port but > >the > > This is fine, ClamD has to listen on a port otherwise no program would be > able to communicate with it. The port should be identical with the one > listed in the clamd.pid file in case you're using it.
I'm not sure about this. The port is not usable, I did use telnet on it and it connects but does not respond to anything (ping, version) and then disconnects... at the same time clamd log shows an error "select() error..." On the other hand, if clamd _needed_ a TCP port it should be one we could configure (my configuration has the TCP port commented out, only the socket is defined), to avoid the exact problem I had with Tripplite's program complaining that the port it uses was not free. > >port number varies) and also on 1,467 UDP ports? > > I was just about asking the same question. Over time ClamD (not FreshClam) > opens (and leaves open) more and more UDP connections. Environment is > Cygwin, latest Cygwin1.dll snapshot version & latest (dev) versions of gcc > and modules. It helps to know I'm not the only one seeing this odd behavior; this could be a bug inside Cygwin if nobody else has seen this in other operating systems. I'll check and see if that's the problem. Regards, -- René Berber _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
