Re: How to know PID responsible for network connection/listen?

2007-11-17 Thread Matthias Apitz
El día Thursday, November 15, 2007 a las 11:20:30AM -0800, Yuri escribió: 'netstat -a' gives me the listing of network connection/listening records. But there's no link to the process id that opened it. With lots of processes this can be a significant problem to figure out who opened which

Re: How to know PID responsible for network connection/listen?

2007-11-17 Thread Tino Engel
Matthias Apitz schrieb: El día Thursday, November 15, 2007 a las 11:20:30AM -0800, Yuri escribió: 'netstat -a' gives me the listing of network connection/listening records. But there's no link to the process id that opened it. With lots of processes this can be a significant problem to

Re: How to know PID responsible for network connection/listen?

2007-11-17 Thread Chuck Robey
Tino Engel wrote: Matthias Apitz schrieb: El día Thursday, November 15, 2007 a las 11:20:30AM -0800, Yuri escribió: 'netstat -a' gives me the listing of network connection/listening records. But there's no link to the process id that opened it. With lots of processes this can be a

How to know PID responsible for network connection/listen?

2007-11-15 Thread Yuri
'netstat -a' gives me the listing of network connection/listening records. But there's no link to the process id that opened it. With lots of processes this can be a significant problem to figure out who opened which connection. Yuri ___

Re: How to know PID responsible for network connection/listen?

2007-11-15 Thread Dan Nelson
In the last episode (Nov 15), Yuri said: 'netstat -a' gives me the listing of network connection/listening records. But there's no link to the process id that opened it. With lots of processes this can be a significant problem to figure out who opened which connection. Try /usr/bin/sockstat

Re: How to know PID responsible for network connection/listen?

2007-11-15 Thread Brian A Seklecki (Mobile)
On Thu, 2007-11-15 at 11:20 -0800, Yuri wrote: 'netstat -a' gives me the listing of network connection/listening records. But there's no link to the process id that opened it. Install ports/sysutils/lsof/ Each socket is a file descriptor. ~BAS With lots of processes this can be a