Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!world!bzs From: bzs@world.std.com (Barry Shein) Newsgroups: comp.unix.internals Subject: Re: How do you find the symbolic links to files. Message-ID: Date: 26 Nov 90 04:56:23 GMT References: <4899@trantor.harris-atd.com> <4900@trantor.harris-atd.com> <12553@medusa.cs.purdue.edu> Sender: bzs@world.std.com (Barry Shein) Organization: The World Lines: 23 In-Reply-To: spaf@cs.purdue.EDU's message of 25 Nov 90 19:32:04 GMT >Somewhat faster, but requiring root access, you can use the "ncheck" >command if your system has it: > ># ncheck -i 4924 /dev/rsd1c > >-- >Gene Spafford Three cheers for V6 commands...I just used ncheck tonight to unscrew a file system (well, figure out what fsck was complaining about with some dup'd inodes, ncheck told me the exact paths so I could jot them down and make sure the files were on backup tape just in case, before clearing them, certainly lessened the confusion.) If your system has them I heartily recommend to everyone reading the manual pages for ncheck, dcheck and icheck before you need them. Oft overlooked tools to use before you start saying yes to fsck. -- -Barry Shein Software Tool & Die | {xylogics,uunet}!world!bzs | bzs@world.std.com Purveyors to the Trade | Voice: 617-739-0202 | Login: 617-739-WRLD