On Mon, 2008-04-07 at 21:00 +0200, Julien Cassette wrote: > 2008/4/6 Kyle Liddell <[EMAIL PROTECTED]>: > > Have you tried passing the -p option to netstat? That should show you what > > program/pid opened each port. > > > > > > On Sun, Apr 06, 2008 at 10:51:47PM +0200, Julien Cassette wrote: > > > Hi, > > > I see many lines similar to these ones in my netstat: > > > > > > tcp 0 0 localhost:9050 localhost:48065 > > > TIME_WAIT - > > > > > > > > Is it a security issue? > > > > > > Regards. > > -- > > [email protected] mailing list > > > > > > Yes, I tried but obviously these sockets aren't owned by a particular program. > See http://rafb.net/p/l7Ykp653.html > > I haven't been following this thread but you can check to see what program is using a port with the fuser command. As root:
# fuser -n tcp 9050 will output a list of PIDs that are using port 9050. You could then pipe that to the ps command to see the process. Something like: # fuser -n tcp 9050 | xargs ps --pid will show the list of processes with port 9050 open. Brett -- [email protected] mailing list
