From: firstname.lastname@example.org (Linus Torvalds)
Subject: Re: Documenting stat(2)
Date: 17 Jan 2001 22:46:11 -0800
In article <20010118002812.A19810@thyrsus.com>,
Eric S. Raymond <email@example.com> wrote:
>* For a socket or FIFO (S_IFSOCK, S_IFIFO) it reports the count of bytes
>waiting to be read.
Don't depend on it. That's pretty much implementation-defined: use the
FIONREAD ioctl to fetch available info from pipes, sockets, ttys etc.
Some versions of Linux will _not_ give the size of the pipe from stat(),
if I remember correctly. And as far as I know, no version of Linux will
have st_size mean anything at all for sockets (pipes, yes. Both named
and unnamed - at least with the current implementation. But not
sockets. How could, it, anyway, as a socket name is nothing but a bind
entry, and can have many sockets associated with it?).
>* For a block special device (S_IFBLK) it returns 0.
Again, this is not something you should depend on. Older Linuxes tried
to return the size of the block device, again if my memory serves me.
>I don't know what it should be expected to return for terminal or
>other special devices. My guess is number of characters waiting
Nope. Use FIONREAD for that.
Linux will normally return 0.
>Can anyone verify, correct, or expand on the above? Reply to
>firstname.lastname@example.org, please, and thanks in advance.
Basically, the _only_ think you should depend on is that st_size
- for regular files, the size of the file in bytes
- for symlinks, the length of the symlink.
That's it. Anybody who tries to use anything else is nonportable, and is
almost guaranteed to not work reliably even on just different versions
of Linux, never mind anything else.