Manpage of PREAD
PREADSection: Linux Programmer's Manual (2)
NAMEpread, pwrite - read from or write to a file descriptor at a given offset
ssize_t pread(int fd, void *buf, size_t count, off_t offset);
ssize_t pwrite(int fd, const void *buf, size_t count, off_t offset);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
- _XOPEN_SOURCE >= 500
|| /* Since glibc 2.12: */ _POSIX_C_SOURCE >= 200809L
DESCRIPTIONpread() reads up to countbytes from file descriptor fdat offset offset(from the start of the file) into the buffer starting at buf. The file offset is not changed.
pwrite() writes up to countbytes from the buffer starting at bufto the file descriptor fdat offset offset. The file offset is not changed.
RETURN VALUEOn success, pread() returns the number of bytes read (a return of zero indicates end of file) and pwrite() returns the number of bytes written.
ERRORSpread() can fail and set errnoto any error specified for read(2) or lseek(2). pwrite() can fail and set errnoto any error specified for write(2) or lseek(2).
VERSIONSThe pread() and pwrite() system calls were added to Linux in version 2.1.60; the entries in the i386 system call table were added in 2.1.69. C library support (including emulation using lseek(2) on older kernels without the system calls) was added in glibc 2.1.
CONFORMING TOPOSIX.1-2001, POSIX.1-2008.
NOTESThe pread() and pwrite() system calls are especially useful in multithreaded applications. They allow multiple threads to perform I/O on the same file descriptor without being affected by changes to the file offset by other threads.
C library/kernel differencesOn Linux, the underlying system calls were renamed in kernel 2.6: pread() became pread64(), and pwrite() became pwrite64(). The system call numbers remained the same. The glibc pread() and pwrite() wrapper functions transparently deal with the change.
On some 32-bit architectures, the calling signature for these system calls differ, for the reasons described in syscall(2).
BUGSPOSIX requires that opening a file with the O_APPENDflag should have no effect on the location at which pwrite() writes data. However, on Linux, if a file is opened with O_APPEND, pwrite() appends data to the end of the file, regardless of the value of offset.
SEE ALSOlseek(2), read(2), readv(2), write(2)
- RETURN VALUE
- CONFORMING TO
- SEE ALSO
This document was created by man2html, using the manual pages.
Time: 22:27:44 GMT, June 20, 2016