Hi,

I want to kill TCP connections which have status as TIME_WAIT & no PID

(as per the output of the "netstat - p" command).

The problem is that these connections don't have process ID (see below).
====================================================================
[remedy@CNDAUNREDBOP13 ~]$ netstat -p |grep 56000
tcp 0 0 CNDAUNREDBOP13:59388 10.5.45.39:56000 TIME_WAIT -
tcp 0 0 CNDAUNREDBOP13:59389 10.5.45.39:56000 TIME_WAIT -
tcp 0 0 CNDAUNREDBOP13:59390 10.5.45.39:56000 TIME_WAIT -
tcp 0 0 CNDAUNREDBOP13:59385 10.5.45.39:56000 TIME_WAIT -
tcp 0 0 CNDAUNREDBOP13:59386 10.5.45.39:56000 TIME_WAIT -
tcp 0 0 CNDAUNREDBOP13:59411 10.5.45.39:56000 TIME_WAIT -
====================================================================

Hi,

Just check if it's not a software service running, sub-service, or hiddent software listener linked to an application or such.

They are closed. The TIME-WAIT state is a precaution against connections being reopened by old duplicate packets, or new connections being corrupted.

Try
netstat -a -n -t and check that what is Local address and Foreign address of those connection and investigate further.

Hi,

I know which application is leavig these open connections.It is actually a shell script file that picks up data from one server & sends it to another server.

Since these connections are not having any pid, i cant kill these connections.
These connections are also not shown as the output of "lsof -i tcp:56000" command.

Can i put a timeout interval for these TIME_WAIT connections?

You change change tcp keepalive using following command
echo 2300 > /proc/sys/net/ipv4/tcp_keepalive_time

thanks

There is a timeout of 4 minutes. From you description it is working perfectly, what problem are you having?

Which not what was asked.

My main concern is tcp connections with status as "TIME_WAIT" which i dont want.

Do you really want to destroy the reliability of TCP? Read RFC 1337 for some examples of what can go wrong if you get rid the TIME-WAIT state.