svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
aio_write(2)
The system call allows the calling process to write from the
buffer pointed to by to the descriptor The call returns immedi‐
ately after the write request has been enqueued to the descrip‐
tor; the write may or may not have completed at the time the call
returns. If the request could not be enqueued, generally due to
invalid arguments, the call returns without having enqueued the
request. If is set for operations append to the file in the same
order as the calls were made. If is not set for the file de‐
scriptor, the write operation will occur at the absolute position
from the beginning of the file plus If is defined, and the de‐
scriptor supports it, then the enqueued operation is submitted at
a priority equal to that of the calling process minus The pointer
may be subsequently used as an argument to and in order to deter‐
mine return or error status for the enqueued operation while it
is in progress. If the request is successfully enqueued, the
value of can be modified during the request as context, so this
value must not be referenced after the request is enqueued. The
structure can be used to request notification of the operation's
completion as described in The Asynchronous I/O Control Block
structure pointed to by and the buffer that the member of that
structure references must remain valid until the operation has
completed. The asynchronous I/O control buffer should be zeroed
before the system call to avoid passing bogus context information
to the kernel. Modifications of the Asynchronous I/O Control
Block structure or the buffer contents are not allowed while the
request is queued. If the file offset in is past the offset max‐
imum for no I/O will occur. The system call will fail if: The
request was not queued because of system resource limitations.
The asynchronous notification method in is invalid or not sup‐
ported. Asynchronous write operations on the file descriptor are
unsafe and unsafe asynchronous I/O operations are disabled. The
following conditions may be synchronously detected when the sys‐
tem call is made, or asynchronously, at any time thereafter. If
they are detected at call time, returns -1 and sets appropri‐
ately; otherwise the system call must be called, and will return
-1, and must be called to determine the actual value that would
have been returned in The argument is invalid, or is not opened
for writing. The offset is not valid, the priority specified by
is not a valid priority, or the number of bytes specified by is
not valid. If the request is successfully enqueued, but subse‐
quently canceled or an error occurs, the value returned by the
system call is per the system call, and the value returned by the
system call is either one of the error returns from the system
call, or one of: The argument is invalid for writing. The re‐
quest was explicitly canceled via a call to The offset would be
invalid. The system call is expected to conform to the standard.
The system call first appeared in This manual page was written by
Invalid information in may confuse the kernel.