| Skip Navigation Links | |
| Exit Print View | |
 | man pages section 3: Basic Library Functions Oracle Solaris 11 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
| man pages section 3: Basic Library Functions Oracle Solaris 11 Information Library |
enable_extended_FILE_stdio(3C)
posix_spawnattr_getschedparam(3C)
posix_spawnattr_getschedpolicy(3C)
posix_spawnattr_getsigdefault(3C)
posix_spawnattr_getsigignore_np(3C)
posix_spawnattr_getsigmask(3C)
posix_spawnattr_setschedparam(3C)
posix_spawnattr_setschedpolicy(3C)
posix_spawnattr_setsigdefault(3C)
posix_spawnattr_setsigignore_np(3C)
posix_spawnattr_setsigmask(3C)
posix_spawn_file_actions_addclose(3C)
posix_spawn_file_actions_addclosefrom_np(3C)
posix_spawn_file_actions_adddup2(3C)
posix_spawn_file_actions_addopen(3C)
posix_spawn_file_actions_destroy(3C)
posix_spawn_file_actions_init(3C)
pthread_attr_getdetachstate(3C)
pthread_attr_getinheritsched(3C)
pthread_attr_getschedparam(3C)
pthread_attr_getschedpolicy(3C)
pthread_attr_setdetachstate(3C)
pthread_attr_setinheritsched(3C)
pthread_attr_setschedparam(3C)
pthread_attr_setschedpolicy(3C)
pthread_barrierattr_destroy(3C)
pthread_barrierattr_getpshared(3C)
pthread_barrierattr_setpshared(3C)
pthread_condattr_getpshared(3C)
pthread_condattr_setpshared(3C)
pthread_cond_reltimedwait_np(3C)
pthread_key_create_once_np(3C)
pthread_mutexattr_getprioceiling(3C)
pthread_mutexattr_getprotocol(3C)
pthread_mutexattr_getpshared(3C)
pthread_mutexattr_getrobust(3C)
pthread_mutexattr_setprioceiling(3C)
pthread_mutexattr_setprotocol(3C)
pthread_mutexattr_setpshared(3C)
pthread_mutexattr_setrobust(3C)
pthread_mutex_getprioceiling(3C)
pthread_mutex_reltimedlock_np(3C)
pthread_mutex_setprioceiling(3C)
pthread_rwlockattr_destroy(3C)
pthread_rwlockattr_getpshared(3C)
pthread_rwlockattr_setpshared(3C)
pthread_rwlock_reltimedrdlock_np(3C)
pthread_rwlock_reltimedwrlock_np(3C)
pthread_rwlock_timedrdlock(3C)
pthread_rwlock_timedwrlock(3C)
rctlblk_get_enforced_value(3C)
- asynchronous write to a file
#include <aio.h>intaio_write(struct aiocb *aiocbp);
Theaio_write() function allows the calling process to writeaiocbp->aio_nbytes to thefile associated withaiocbp->aio_fildes from the buffer pointed to byaiocbp->aio_buf. Thefunction call returns when the write request has been initiated or, ata minimum, queued to the file or device. If_POSIX_PRIORITIZED_IO is definedand prioritized I/O is supported for this file, then the asynchronous operationis submitted at a priority equal to the scheduling priority of the processminusaiocbp->aio_reqprio. Theaiocbp may be used as an argument toaio_error(3C)andaio_return(3C) in order to determine the error status and return status,respectively, of the asynchronous operation while it is proceeding.
Theaiocbp argument points to anaiocb structure. If the buffer pointedto byaiocbp->aio_buf or the control block pointed to byaiocbp becomesan illegal address prior to asynchronous I/O completion, then the behavior is undefined.
IfO_APPEND is not set for the file descriptoraio_fildes, then therequested operation takes place at the absolute position in the file asgiven byaio_offset, as iflseek(2) were called immediately prior to theoperation with anoffset equal toaio_offset and awhence equal toSEEK_SET. IfO_APPEND is set for the file descriptor, write operations appendto the file in the same order as the calls were made.After a successful call to enqueue an asynchronous I/O operation, the valueof the file offset for the file is unspecified.
Theaiocbp->aio_sigevent structure defines what asynchronous notification is to occur when theasynchronous operation completes, as specified insignal.h(3HEAD).
Theaiocbp->aio_lio_opcode field is ignored byaio_write().
Simultaneous asynchronous operations using the sameaiocbp produce undefined results.
If_POSIX_SYNCHRONIZED_IO is defined and synchronized I/O is enabled on the fileassociated withaiocbp->aio_fildes, the behavior of this function shall be according tothe definitions of synchronized I/O data integrity completion and synchronized I/O file integritycompletion.
For any system action that changes the process memory space while anasynchronous I/O is outstanding to the address range being changed, the resultof that action is undefined.
For regular files, no data transfer will occur past the offset maximumestablished in the open file description associated withaiocbp->aio_fildes.
Theaio_write() function returns0 to the calling process if the I/Ooperation is successfully queued; otherwise, the function returns-1 and setserrnoto indicate the error.
Theaio_write() function will fail if:
The requested asynchronous I/O operation was not queued due to system resource limitations.
Each of the following conditions may be detected synchronously at the timeof the call toaio_write(), or asynchronously. If any of the conditionsbelow are detected synchronously, theaio_write() function returns-1 and setserrnoto the corresponding value. If any of the conditions below are detectedasynchronously, the return status of the asynchronous operation is set to-1,and the error status of the asynchronous operation will be set tothe corresponding value.
Theaiocbp->aio_fildes argument is not a valid file descriptor open for writing.
The file offset value implied byaiocbp->aio_offset would be invalid,aiocbp->aio_reqprio is not a valid value, oraiocbp->aio_nbytes is an invalid value.
In the case that theaio_write() successfully queues the I/O operation, thereturn status of the asynchronous operation will be one of the valuesnormally returned by thewrite(2) function call. If the operation is successfullyqueued but is subsequently canceled or encounters an error, the error statusfor the asynchronous operation contains one of the values normally set bythewrite() function call, or one of the following:
Theaiocbp->aio_fildes argument is not a valid file descriptor open for writing.
The file offset value implied byaiocbp->aio_offset would be invalid.
The requested I/O was canceled before the I/O completed due to an explicitaio_cancel(3C) request.
The following condition may be detected synchronously or asynchronously:
The file is a regular file,aiobcp->aio_nbytes is greater than 0 and the starting offset inaiobcp->aio_offset is at or beyond the offset maximum in the open file description associated withaiocbp->aio_fildes.
Theaio_write() function has a transitional interface for 64-bit file offsets. Seelf64(5).
Seeattributes(5) for descriptions of the following attributes:
|
aio_cancel(3C),aio_error(3C),aio_read(3C),aio_return(3C),lio_listio(3C),close(2),_Exit(2),fork(2),lseek(2),write(2),aio.h(3HEAD),signal.h(3HEAD),attributes(5),lf64(5),standards(5)
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.Legal Notices |   |