My start configuration as set up at booting:
Code:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2032/portmap
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 2358/xinetd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2372/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2172/cupsd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2289/master
tcp 0 0 127.0.0.1:7572 127.0.0.1:111 TIME_WAIT -
tcp 0 0 :::22 :::* LISTEN 2372/sshd
tcp 0 0 ::1:631 :::* LISTEN 2172/cupsd
tcp 0 0 ::1:25 :::* LISTEN 2289/master
ftp access not possible, no trace in /var/log/xinetd.log,/var/log/messages
Stopping xinetd and starting pure-ftpd:
Code:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2032/portmap
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 2941/pure-ftpd (SER
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2372/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2172/cupsd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2289/master
tcp 0 0 :::21 :::* LISTEN 2941/pure-ftpd (SER
tcp 0 0 :::22 :::* LISTEN 2372/sshd
tcp 0 0 ::1:631 :::* LISTEN 2172/cupsd
tcp 0 0 ::1:25 :::* LISTEN 2289/master
ftp access not possible, no trace in /var/log/messages
Conclusion:
It is not really a problem with xinetd/pure-ftpd, the problem is upstream with the basic tcp handling!