Mac Developer Library Developer


This manual page is part of Xcode Tools version 5.0

To obtain these tools:

If you are running a version of Xcode Tools other than 5.0, 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.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

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

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

IOCTL(2)                    BSD System Calls Manual                   IOCTL(2)

     ioctl -- control device

     #include <sys/ioctl.h>

     ioctl(int fildes, unsigned long request, ...);

     The ioctl() function manipulates the underlying device parameters of special files.  In particular,
     many operating characteristics of character special files (e.g. terminals) may be controlled with
     ioctl() requests.  The argument fildes must be an open file descriptor.

     An  ioctl request has encoded in it whether the argument is an ``in'' parameter or ``out'' parameter,
     and the size of the argument argp in bytes.  Macros and defines used in specifying an ioctl request are
     located in the file <sys/ioctl.h>.

     If an error has occurred, a value of -1 is returned and errno is set to indicate the error.

     Ioctl() will fail if:

     [EBADF]            fildes is not a valid descriptor.

     [EINVAL]           Request or argp is not valid.

     [ENOTTY]           fildes is not associated with a character special device.

     [ENOTTY]           The specified request does not apply to the kind of object that the descriptor
                        fildes references.

     cdio(1), chio(1), mt(1), execve(2), fcntl(2), intro(4), tty(4)

     An ioctl() function call appeared in Version 7 AT&T UNIX.

4th Berkeley Distribution      December 11, 1993     4th Berkeley Distribution

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.