Main index | Section 2 | 日本語 | Options |
#include <unistd.h>
#include <sys/uio.h>
For writev() and pwritev(), the iovec structure is defined as:
struct iovec { void *iov_base; /* Base address. */ size_t iov_len; /* Length. */ };
Each iovec entry specifies the base address and length of an area in memory from which data should be written. The writev() system call will always write a complete area before proceeding to the next.
On objects capable of seeking, the write() starts at a position given by the pointer associated with fd, see lseek(2). Upon return from write(), the pointer is incremented by the number of bytes which were written.
Objects that are not capable of seeking always write from the current position. The value of the pointer associated with such an object is undefined.
If the real user is not the super-user, then write() clears the set-user-id bit on a file. This prevents penetration of system security by a user who "captures" a writable set-user-id file owned by the super-user.
When using non-blocking I/O on objects such as sockets that are subject to flow control, write() and writev() may write fewer bytes than requested; the return value must be noted, and the remainder of the operation should be retried when possible.
[EBADF] | |
The fd argument is not a valid descriptor open for writing. | |
[EPIPE] | |
An attempt is made to write to a pipe that is not open for reading by any process. | |
[EPIPE] | |
An attempt is made to write to a socket of type SOCK_STREAM that is not connected to a peer socket. | |
[EFBIG] | |
An attempt was made to write a file that exceeds the process's file size limit or the maximum file size. | |
[EFAULT] | |
Part of iov or data to be written to the file points outside the process's allocated address space. | |
[EINVAL] | |
The pointer associated with fd was negative. | |
[ENOSPC] | |
There is no free space remaining on the file system containing the file. | |
[EDQUOT] | |
The user's quota of disk blocks on the file system containing the file has been exhausted. | |
[EIO] | An I/O error occurred while reading from or writing to the file system. |
[EINTR] | |
A signal interrupted the write before it could be completed. | |
[EAGAIN] | |
The file was marked for non-blocking I/O, and no data could be written immediately. | |
[EROFS] | |
An attempt was made to write over a disk label area at the beginning
of a slice.
Use
disklabel(8)
| |
[EINVAL] | |
The value nbytes is greater than SSIZE_MAX (or greater than INT_MAX, if the sysctl debug.iosize_max_clamp is non-zero). | |
[EINTEGRITY] | |
The backing store for fd detected corrupted data while reading. (For example, writing a partial filesystem block may require first reading the existing block which may trigger this error.) | |
In addition, writev() and pwritev() may return one of the following errors:
[EDESTADDRREQ] | |
The destination is no longer available when writing to a Unix domain datagram socket on which connect(2) had been used to set a destination address. | |
[EINVAL] | |
The iovcnt argument was less than or equal to 0, or greater than IOV_MAX. | |
[EINVAL] | |
One of the iov_len values in the iov array was negative. | |
[EINVAL] | |
The sum of the iov_len values in the iov array overflowed a 32-bit integer. | |
[ENOBUFS] | |
The mbuf pool has been completely exhausted when writing to a socket. | |
The pwrite() and pwritev() system calls may also return the following errors:
[EINVAL] | |
The offset value was negative. | |
[ESPIPE] | |
The file descriptor is associated with a pipe, socket, or FIFO. | |
WRITE (2) | February 11, 2021 |
Main index | Section 2 | 日本語 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
“ | I think Unix and snowflakes are the only two classes of objects in the universe in which no two instances ever match exactly. | ” |
— Noel Chiappa |