Any idea how long these idle ports stick around? ...I would have
thought they would not be in the idle state but wait_close or
something terminal.
I'm trying to track down issues where the system runs out of file
descriptors.

java_q3p 29846 root 88u IPv4 0x626ac640 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 89u IPv4 0x6176c0c0 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 90u IPv4 0x5dbfe4c0 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 91u IPv4 0x61294280 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 92u IPv4 0x59c2a200 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 93u IPv4 0x5def3940 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 94u IPv4 0x5dd31e40 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 95u IPv4 0x5b538580 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 96u IPv4 0x61737b00 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 97u IPv4 0x61666e80 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 98u IPv4 0x5cce5540 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 99u IPv4 0x61419940 0t0 TCP *:*
(IDLE)
java_q3p 29846 root 100u IPv4 0x607536c0 0t0 TCP *:*
(IDLE)



On Nov 25, 10:45 am, Ht <hung...@gmail.com> wrote:
> I see what you mean Alain. They point to a file that has been
> deleted...but i thought i'd see one of them not the dozens i'm
> seeing...which I'm trying to explain. I actually see the number
> increasing over time. I'm almost wondering if I've got a leak in some
> file reader.
>
> On Nov 25, 10:15 am, Alain <ota1...@hotmail.com> wrote:
>
> > Ht a écrit :
>
> > > Does this describe multiple open files or the same one? They point to
> > > the same device and some node name...
>
> > > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> > > java 2264 root 208u REG 64,0x5 3079 38214 /opt
> > > (/dev/vg00/lvol5)
> > > java 2264 root 209u REG 64,0x5 3079 38214 /opt
> > > (/dev/vg00/lvol5)
>
> > Same inode: 38214 which is a directory (/opt). In my opinion, nothing to
> > worry about.
> > Try "ls -lid /opt" to get /opt'inode.
> > lsof is useful to find which process is listening at a port; we use it
> > also to find removed huge file but still hold by a process,...