Return to BSD News archive
Xref: sserve comp.protocols.tcp-ip:31297 comp.unix.aix:43136 comp.sys.hp.hpux:11091 comp.unix.sys5.r4:8219 comp.unix.bsd:14726 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!pipex!news.maz.net!haegar.allcon.net!gurke.allcon.com!morten Date: 26 Aug 1994 10:29:00 +0100 From: morten@gurke.allcon.com (Morten Jammer) Newsgroups: comp.protocols.tcp-ip,comp.unix.aix,comp.sys.hp.hpux,comp.unix.sys5.r4,comp.unix.bsd Message-ID: <5VapHfY2-DB@gurke.allcon.com> References: <33jc7q$3gk@news.cerf.net> Subject: Re: sock to proc? X-Newsreader: XP v3.02 X-Charset: ISO-8859-1 Lines: 17 escneto@cerfnet.com hielt es für nötig am 25.08.94 zum Thema "sock to proc?" folgendes von sich zu geben: > Question. Given a pointer to a socket in the kernels address space, how > can I go about finding the process which owns the socket? Try OFILES or LSOF, which gives you the PID of the process holding the connection. You need the number of the transmission controll block. - morten : Morten Jammer : Ich sei, gewährt mir die Bitte : Norderstrasse 97: in eurem Netzwerk : 24939 Flensburg : der Dritte ## CrossPoint v3.02 ##