Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!gatech!hao!boulder!cdash
From: cdash@boulder.UUCP
Newsgroups: comp.unix.questions
Subject: Re: A couple questions
Message-ID: <634@boulder.Colorado.EDU>
Date: Wed, 6-May-87 19:37:48 EDT
Article-I.D.: boulder.634
Posted: Wed May  6 19:37:48 1987
Date-Received: Fri, 8-May-87 04:35:23 EDT
References: <3164@jade.BERKELEY.EDU> <2382@ncoast.UUCP> <1752@dg_rtp.UUCP> <816@killer.UUCP> <5835@brl-smoke.ARPA>
Reply-To: cdash@boulder.Colorado.EDU (Charles Shub)
Organization: University of Colorado at Colorado Springs
Lines: 17

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.

actually, it is possible. you know the inode associated with the descriptor
start at "/" and just keep looking for that i# keeping track of where you are.
Like the man said, it ain't easy, but it CAN be done.
-- 


cdash   aka cdash@boulder.colorado.edu    aka ...hao!boulder!cdash
	aka ...nbires!boulder!cdash