READ
2
1997-07-12
Linux 2.0.32
Linux Programmer's Manual
count bytes from file descriptor fd into the buffer starting at buf . If count is zero, read() returns zero and has no other results. If count is greater than SSIZE_MAX, the result is unspecified.
file), and the file position is advanced by this number. It is not an error if this number is smaller than the number of bytes requested; this may happen for example because fewer bytes are actually available right now (maybe because we were close to end-of-file, or because we are reading from a pipe, or from a terminal), or because read() was interrupted by a signal. On error, -1 is returned, and errno is set appropriately. In this case it is left unspecified whether the file position (if any) changes.
time stamp the first time, subsequent calls may not do so. This is caused by client side attribute caching, because most if not all NFS clients leave atime updates to the server and client side reads satisfied from the client's cache will not cause atime updates on the server as there are no server side reads. UNIX semantics can be obtained by disabling client side attribute caching, but in most situations this will substantially increase server load and decrease performance. Many filesystems and disks were considered to be fast enough that the implementation of O_NONBLOCK was deemed unneccesary. So, O_NONBLOCK may not be available on files and/or disks.
fcntl(2) , ioctl(2) , lseek(2) , readdir(2) , readlink(2) , select(2) , write(2) , fread(3) , readv(3) |
||||||||||