Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site rlgvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!teddy!panda!talcott!harvard!seismo!rlgvax!guy
From: guy@rlgvax.UUCP (Guy Harris)
Newsgroups: net.unix
Subject: Re: How can I find where a link leads to (find -inum feature)
Message-ID: <353@rlgvax.UUCP>
Date: Mon, 14-Jan-85 23:42:37 EST
Article-I.D.: rlgvax.353
Posted: Mon Jan 14 23:42:37 1985
Date-Received: Thu, 17-Jan-85 03:46:05 EST
References: <1886@inmet.UUCP>
Organization: CCI Office Systems Group, Reston, VA
Lines: 17

> Granted you have found the inode number via:
> 	ls -i
> one can then use find with the -inum option to
> locate all the directory entries.
> Note that a find from / can take a veryyyyyyyy longgggggg time.

(BTW, "find -inum" is in all the version of "find" I've seen, although
Berkeley are the only people who bothered documenting it.)  In addition to
being slow, this 1) may have several false hits, as it looks for all files
with that inumber regardless of what file system they're on and 2) also may
not work if some of the directory entries pointing to that inode are in
directories that you have no read access to.  You could run it as superuser,
but then if you can run as superuser you should use "ncheck" which is lots
faster and searches only one filesystem (thus eliminating problems 1) and 2)).

	Guy Harris
	{seismo,ihnp4,allegra}!rlgvax!guy