hpux man page for aio_fsync

aio_fsync(2)							System Calls Manual						      aio_fsync(2)

NAME
       aio_fsync() - force outstanding asynchronous operations on a file to the synchronized state

SYNOPSIS
DESCRIPTION
       The function asynchronously forces all I/O operations that are enqueued at the time of the call for the file or device referenced by to the
       synchronized I/O state.	The function call returns when the synchronization request has been enqueued to the file or device (even when  the
       data cannot be synchronized immediately).

       Successful  completion  of  the	request  indicates  that all modified data for has been moved to a permanent storage device.  The function
       affects only those asynchronous I/O operations enqueued at the time of the call.  Subsequently enqueued operations are not included in  the
       synchronizing operation.

       The function supports synchronized I/O for regular files, block special files, and character special files.

       If  the	is all currently enqueued asynchronous I/O operations for are completed as if by a call to All data is forced to permanent storage
       but the meta-data (such as modification times) for the file descriptor is not necessarily updated.  If the is all currently enqueued  asyn-
       chronous  I/O  operations  for are completed as if by a call to All data is forced to permanent storage and the file descriptor metadata is
       updated.

       If an request is issued for a file when there is already a pending request, the first request is treated as though it were part of the sec-
       ond, and the second request will not complete until the first has completed.

       The  function  returns  when  the  fsync  request  has  been enqueued for the referenced file or device.  The and functions must be used to
       retrieve the status of the synchronization operation via the referenced by The status returned will be until the last  operation  addressed
       by the initial request completes.  If all operations complete successfully, the error status will be 0 (zero).  Otherwise, the error status
       will be the error status that will be returned for the read or write operation that failed.

       If is a valid signal event structure, then the designated signal will be delivered when the requested synchronization operation	completes,
       either when all subject requests have completed successfully or when any one of the requests has failed.

       To use this function, link in the realtime library by specifying on the compiler or linker command line.

RETURN VALUE
       If the function fails, is returned and is set to indicate the error.

ERRORS
       If detects one of the following error conditions, is set to the indicated value:

	      [EAGAIN]	     The  request  could  not be queued because a per-process or system-wide limit on asynchronous I/O operations or asyn-
			     chronous threads would have been exceeded.

	      [EBADF]	     The is not a valid file descriptor open for writing.

	      [EINVAL]	     Synchronized I/O is not supported for the file specified by

	      [EINVAL]	     The is not a valid address in the process virtual address space.

	      [EINVAL]	     The parameters of the indicated in are invalid.

SEE ALSO
       aio_cancel(2), aio_error(2), aio_read(2), aio_return(2), aio_suspend(2),  aio_write(2),	fdatasync(2),  fsync(2),  lio_listio(2),  read(2),
       write(2), aio(5).

STANDARDS CONFORMANCE
																      aio_fsync(2)