4 messages in org.freebsd.freebsd-fsfstat and filenames| From | Sent On | Attachments |
|---|---|---|
| Denis Eremenko | Dec 11, 2007 9:39 pm | |
| Lowell Gilbert | Dec 14, 2007 6:21 am | |
| Denis Eremenko | Dec 20, 2007 7:11 pm | |
| Robert Watson | Dec 21, 2007 5:28 pm |
| Subject: | fstat and filenames | |
|---|---|---|
| From: | Denis Eremenko (moon...@pnhz.kz) | |
| Date: | Dec 20, 2007 7:11:08 pm | |
| List: | org.freebsd.freebsd-fs | |
? ??, 14/12/2007 ? 09:03 -0500, Lowell Gilbert ?????:
moon...@pnhz.kz (Denis Eremenko) writes:
Why fstat so secretive about file names and unix domain sockets?
With respect to file names, you need to remember that there may not be a unique answer. A file handle's metadata doesn't keep information about how it was opened, just the inode. That inode could belong to multiple directory entries, or none -- this is why, as the fstat(1) manual points out, "there is no mapping from an open file back to the directory entry that was used to open that file."
Yes. I clearly understand difficulties of exact inode-name mapping. And i saw manpage note too. But doesn't _some_and_maybe_wrong_ information better than nothing? Additionally - most files has one filesystem record.
As far as unix domain sockets, I don't understand the question. Sorry.
fstat doesn't show their names too.