This manual page is part of Xcode Tools version 3.2

To obtain these tools:

If you are running a version of Xcode Tools other than 3.2, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • For more information about the manual page format, see the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Reference Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.


AIO_ERROR(2)                               BSD System Calls Manual                              AIO_ERROR(2)

NAME
     aio_error -- retrieve error status of asynchronous I/O operation (REALTIME)

LIBRARY
     Standard C Library (libc, -lc)

SYNOPSIS
     #include <aio.h>

     int
     aio_error(const struct aiocb *aiocbp);

DESCRIPTION
     The aio_error() system call returns the error status of the asynchronous I/O request associated with
     the structure pointed to by aiocbp.

RETURN VALUES
     If the asynchronous I/O request has completed successfully, aio_error() returns 0.  If the request has
     not yet completed, EINPROGRESS is returned.  If the request has completed unsuccessfully, the error
     status is returned as described in read(2), write(2), or fsync(2) is returned.  On failure, aio_error()
     returns -1 and sets errno to indicate the error condition.

ERRORS
     The aio_error() system call will fail if:

     [EINVAL]           The aiocbp argument does not reference an outstanding asynchronous I/O request.

SEE ALSO
     aio_cancel(2), aio_read(2), aio_return(2), aio_suspend(2), aio_write(2), fsync(2), read(2), write(2),
     aio(4)

STANDARDS
     The aio_error() system call is expected to conform to the IEEE Std 1003.1 (``POSIX.1'') standard.

HISTORY
     The aio_error() system call first appeared in FreeBSD 3.0.

AUTHORS
     This manual page was written by Wes Peters <[email protected]>.

BSD                                             June 2, 1999                                             BSD

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.