Return to BSD News archive
Xref: sserve comp.sys.sun.admin:24244 comp.unix.bsd:13260 Newsgroups: comp.sys.sun.admin,comp.unix.bsd Path: sserve!newshost.anu.edu.au!munnari.oz.au!sgiblab!sdd.hp.com!nigel.msen.com!usenet.ins.cwru.edu!howland.reston.ans.net!cs.utexas.edu!uunet!spcuna!spcvxb!terry From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) Subject: Re: How to track down process id from socket port? Nntp-Posting-Host: spcvxa.spc.edu References: <2h165i$rcu@access3.digex.net> Sender: news@spcuna.spc.edu (Network News) Organization: St. Peter's College, US Date: Thu, 13 Jan 1994 08:15:45 GMT Message-ID: <1994Jan13.031545.1@spcvxb.spc.edu> Lines: 17 In article <2h165i$rcu@access3.digex.net>, masato@access3.digex.net (J M Thompson) writes: > I would like to determine which process has opened a particular > tcp socket. For example, from the following output of the > 'netstat -an' command: > > tcp 0 0 *.32160 *.* LISTEN > > I would like to be able to determine the PID for the process that > has tcp socket port 32160 open. It seems to me that the IDENT code does this (and more) in order to hand a remote system the username that's performing the socket operation in ques- tion. You can get the ident sources from ftp.lysator.liu.se. Terry Kennedy Operations Manager, Academic Computing terry@spcvxa.bitnet St. Peter's College, Jersey City, NJ USA terry@spcvxa.spc.edu +1 201 915 9381