01.01.2013 Views

AT&T UNIX™PC Unix System V Users Manual - tenox

AT&T UNIX™PC Unix System V Users Manual - tenox

AT&T UNIX™PC Unix System V Users Manual - tenox

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

INTRO ( 2) INTR0 (2)<br />

the appropriate permissions, does not start with a valid<br />

magic number (see a.out(4)).<br />

9 EBADF Bad file number<br />

Either a file descriptor refers to no open file, or a read<br />

(respectively write) request is made to a file which is open<br />

only for writing (respectively reading).<br />

10 ECHILD No child processes<br />

A wait, was executed by a process that had no existing or<br />

unwaited-for child processes.<br />

11 EAGAIN No more processes<br />

A fork , failed because the system's process table is full or<br />

the user is not allowed to create any more processes.<br />

12 ENOMEM Not enough space<br />

During an exec, brk, or sbrk, a program asks for more<br />

space than the system is able to supply . This is not a<br />

temporary condition; the maximum space size is a system<br />

parameter. The error may also occur if the arrangement<br />

of text, data, and stack segments requires too many segmentation<br />

registers, or if there is not enough swap space<br />

during a fork .<br />

13 EACCES Permission denied<br />

An attempt was made to access a file in a way forbidden<br />

by the protection system.<br />

14 EFAULT Bad address<br />

The system encountered a hardware fault in attempting to<br />

use an argument of a system call.<br />

15 ENOTBLK Block device required<br />

A non-block file was mentioned where a block device was<br />

required, e.g., in mount .<br />

16 EBUSY Mount device busy<br />

An attempt to mount a device that was already mounted<br />

or an attempt was made to dismount a device on which<br />

there · is an active file (open file, current directory,<br />

mounted-on file, active text segment). It will also occur if<br />

an attempt is made to enable accounting when it is<br />

already enabled.<br />

17 EEXIST File exists<br />

An existing file was mentioned in an inappropriate context,<br />

e.g., link .<br />

18 EXDEV Cross-device link<br />

A link to a file on another device was attempted.<br />

19 ENODEV No such device<br />

An attempt was made to apply an inappropriate system<br />

call to a device; e.g., read a write-only device.<br />

20 ENOTDIR Not a directory<br />

A non-directory was specified where a directory is<br />

required, for example in a path prefix or as an argument<br />

to chdir(2).<br />

- 2-

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!