Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbatt!cwruecmp!hal!ncoast!tdi2!brandon
From: brandon@tdi2.UUCP
Newsgroups: comp.unix.questions
Subject: Re: A couple questions
Message-ID: <354@tdi2.UUCP>
Date: Tue, 12-May-87 12:24:10 EDT
Article-I.D.: tdi2.354
Posted: Tue May 12 12:24:10 1987
Date-Received: Sat, 16-May-87 05:09:58 EDT
References: <3164@jade.BERKELEY.EDU> <2382@ncoast.UUCP> <1752@dg_rtp.UUCP> <816@killer.UUCP> <5835@brl-smoke.ARPA>
Reply-To: brandon@tdi2.UUCP (Brandon Allbery)
Organization: Tridelta Industries, Inc., Mentor, Ohio
Lines: 20

In article <5835@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
+---------------
| In article <816@killer.UUCP> jfh@killer.UUCP (John Haugh) writes:
| >If you wanted to, you could even find out the name
| >of the file that was connected to the descriptor.  (It is _not_ easy :-( )
| 
| I would think it's actually impossible.  The kernel doesn't remember
| the name of the path you used to open an inode, and some descriptors
| (e.g. pipes) have no associated names.
+---------------

Well, it's possible for non-pipes; unfortunately, you have to essentially
recode ncheck(1m) to do it.

++Brando
-- 
Brandon S. Allbery	           UUCP: cbatt!cwruecmp!ncoast!tdi2!brandon
Tridelta Industries, Inc.         CSNET: ncoast!allbery@Case
7350 Corporate Blvd.	       INTERNET: ncoast!allbery%Case.CSNET@relay.CS.NET
Mentor, Ohio 44060		  PHONE: +1 216 255 1080 (home +1 216 974 9210)