Yes, all from amuleweb. I wonder if it's a result of something bizarre from my setup. It could be that big brother regularly opens a socket to test the service is up, and then it drops the socket. Maybe amuleweb doesn't like the way that the bb4 client does that.
johnh@shuttle johnh $ netstat -n | grep CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:47120 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:50454 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:43543 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:36116 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:33557 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:34837 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:38171 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:40217 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:47646 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:36636 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:38402 CLOSE_WAIT
tcp 1 0 172.29.0.2:4711 172.29.0.2:48640 CLOSE_WAIT
etc etc etc couple of hundred of lines cut