I get an excessive amount of CLOSE_WAIT's in netstat.
paradise:~# netstat -anop |grep -c CLOSE_WAIT
184
for instance:
netstat -anop
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name Timer
tcp 1 0 192.168.1.1:45317 192.168.1.2:1581 CLOSE_WAIT - off (0.00/0/0)
tcp 1 0 192.168.1.1:49064 192.168.1.2:1827 CLOSE_WAIT - off (0.00/0/0)
tcp 1 0 192.168.1.1:44339 192.168.1.2:1457 CLOSE_WAIT - off (0.00/0/0)
tcp 1 0 192.168.1.1:53426 192.168.1.2:2380 CLOSE_WAIT - off (0.00/0/0)
Where .1 is me, and .2 is the server I am mounting (redhat box running proftpd 1.2.4 2.2,14 kernel) I'm running debian unstable 2.4.17 kernel (dlink 8139 card).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I get an excessive amount of CLOSE_WAIT's in netstat.
paradise:~# netstat -anop |grep -c CLOSE_WAIT
184
for instance:
netstat -anop
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name Timer
tcp 1 0 192.168.1.1:45317 192.168.1.2:1581 CLOSE_WAIT - off (0.00/0/0)
tcp 1 0 192.168.1.1:49064 192.168.1.2:1827 CLOSE_WAIT - off (0.00/0/0)
tcp 1 0 192.168.1.1:44339 192.168.1.2:1457 CLOSE_WAIT - off (0.00/0/0)
tcp 1 0 192.168.1.1:53426 192.168.1.2:2380 CLOSE_WAIT - off (0.00/0/0)
Where .1 is me, and .2 is the server I am mounting (redhat box running proftpd 1.2.4 2.2,14 kernel) I'm running debian unstable 2.4.17 kernel (dlink 8139 card).
I'm using the external modules btw, not the kernel patch.