table of contents
other versions
- wheezy 3.44-1
- jessie 3.74-1
- jessie-backports 4.10-2~bpo8+1
- testing 4.10-2
- unstable 4.10-2
other languages
other sections
WRITE(2) | Linux Programmer's Manual | WRITE(2) |
NAME¶
write - write to a file descriptorSYNOPSIS¶
#include <unistd.h>DESCRIPTION¶
write() writes up to count bytes from the buffer pointed buf to the file referred to by the file descriptor fd.RETURN VALUE¶
On success, the number of bytes written is returned (zero indicates nothing was written). On error, -1 is returned, and errno is set appropriately.ERRORS¶
- EAGAIN
- The file descriptor fd refers to a file other than a socket and has been marked nonblocking (O_NONBLOCK), and the write would block.
- EAGAIN or EWOULDBLOCK
- The file descriptor fd refers to a socket and has been marked nonblocking (O_NONBLOCK), and the write would block. POSIX.1-2001 allows either error to be returned for this case, and does not require these constants to have the same value, so a portable application should check for both possibilities.
- EBADF
- fd is not a valid file descriptor or is not open for writing.
- EDESTADDRREQ
- fd refers to a datagram socket for which a peer address has not been set using connect(2).
- EFAULT
- buf is outside your accessible address space.
- EFBIG
- An attempt was made to write a file that exceeds the implementation-defined maximum file size or the process's file size limit, or to write at a position past the maximum allowed offset.
- EINTR
- The call was interrupted by a signal before any data was written; see signal(7).
- EINVAL
- fd is attached to an object which is unsuitable for writing; or the file was opened with the O_DIRECT flag, and either the address specified in buf, the value specified in count, or the current file offset is not suitably aligned.
- EIO
- A low-level I/O error occurred while modifying the inode.
- ENOSPC
- The device containing the file referred to by fd has no room for the data.
- EPIPE
- fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIGPIPE signal. (Thus, the write return value is seen only if the program catches, blocks or ignores this signal.)
CONFORMING TO¶
SVr4, 4.3BSD, POSIX.1-2001.NOTES¶
A successful return from write() does not make any guarantee that data has been committed to disk. In fact, on some buggy implementations, it does not even guarantee that space has successfully been reserved for the data. The only way to be sure is to call fsync(2) after you are done writing all your data.SEE ALSO¶
close(2), fcntl(2), fsync(2), ioctl(2), lseek(2), open(2), pwrite(2), read(2), select(2), writev(2), fwrite(3)COLOPHON¶
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/.2010-08-29 | Linux |