errors.html

unix 下的C开发手册,还用详细的例程。

A message sent on a transport provider was larger
than an internal message buffer or some other network limit.

<dt>[EMSGSIZE]<dd><index term="EMSGSIZE, "></index>

Inappropriate message buffer length.

<dt>[EMULTIHOP]<dd><index term="EMULTIHOP, "></index>

Reserved

<dt>[ENAMETOOLONG]<dd><index term="ENAMETOOLONG, "></index>

Filename too long

The length of a pathname exceeds {PATH_MAX}, or a pathname component is longer
than {NAME_MAX} and {_POSIX_NO_TRUNC} was in effect for that file.

<dt>[ENETDOWN]<dd><index term="ENETDOWN, "></index>

Network is down

The local interface used to reach the destination is down.

<dt>[ENETUNREACH]<dd><index term="ENETUNREACH, "></index>

Network unreachable

No route to the network is present.

<dt>[ENFILE]<dd><index term="ENFILE, "></index>

Too many files open in system

Too many files are currently open in the system. The system has reached its
predefined limit for simultaneously open files and temporarily cannot
accept requests to open another one.

<dt>[ENOBUFS]<dd><index term="ENOBUFS, "></index>

No buffer space available

Insufficient buffer resources were available in the system to perform
the socket operation.

<dt>[ENODATA]<dd><index term="ENODATA, "></index>

No message available

No message is available on the STREAM head read queue.

<dt>[ENODEV]<dd><index term="ENODEV, "></index>

No such device

An attempt was made to apply an inappropriate function to a device; for
example, trying to read a write-only device such as a printer.

<dt>[ENOENT]<dd><index term="ENOENT, "></index>

No such file or directory

A component of a specified pathname does not exist, or the pathname is an
empty string.

<dt>[ENOEXEC]<dd><index term="ENOEXEC, "></index>

Executable file format error

A request is made to execute a file that, although it has the appropriate
permissions, is not in the format required by the implementation for
executable files.

<dt>[ENOLCK]<dd><index term="ENOLCK, "></index>

No locks available

A system-imposed limit on the number of simultaneous file and record locks
has been reached and no more are currently available.

<dt>[ENOLINK]<dd><index term="ENOLINK, "></index>

Reserved

<dt>[ENOMEM]<dd><index term="ENOMEM, "></index>

Not enough space

The new process image requires more memory than is allowed by the hardware
or system-imposed memory management constraints.


<dt>[ENOMSG]<dd><index term="ENOMSG, "></index>

No message of the desired type

The message queue does not contain a message of the required type
during interprocess communication.

<dt>[ENOPROTOOPT]<dd><index term="ENOPROTOOPT, "></index>

Protocol not available

The protocol option specified to
<i><a href="../xns/setsockopt.html">setsockopt()</a></i>
is not supported by the implementation.

<dt>[ENOSPC]<dd><index term="ENOSPC, "></index>

No space left on a device

During the
<i><a href="write.html">write()</a></i>
function on a regular file or when extending
a directory, there is no free space left on the device.

<dt>[ENOSR]<dd><index term="ENOSR, "></index>

No STREAM resources

Insufficient STREAMS memory resources are available to perform a STREAMS
related function.  This is a temporary condition; one may recover from it if
other processes release resources.

<dt>[ENOSTR]<dd><index term="ENOSTR, "></index>

Not a STREAM

A STREAM function was attempted on a file descriptor that
was not associated with a STREAMS device.

<dt>[ENOSYS]<dd><index term="ENOSYS, "></index>

Function not implemented

An attempt was made to use a function that is not available in this
implementation.

<dt>[ENOTCONN]<dd><index term="ENOTCONN, "></index>

Socket not connected

The socket is not connected.

<dt>[ENOTDIR]<dd><index term="ENOTDIR, "></index>

Not a directory

A component of the specified pathname exists, but it is not a directory,
when a directory was expected.

<dt>[ENOTEMPTY]<dd><index term="ENOTEMPTY, "></index>

Directory not empty

A directory with entries other than dot and dot-dot was supplied when an
empty directory was expected.

<dt>[ENOTSOCK]<dd><index term="ENOTSOCK, "></index>

Not a socket

The file descriptor does not refer to a socket.

<dt>[ENOTSUP]<dd><index term="ENOTSUP, "></index>

Not supported

The implementation does not support this feature of the Realtime
Feature Group.

<dt>[ENOTTY]<dd><index term="ENOTTY, "></index>

Inappropriate I/O control operation

A control function has been attempted for a file or special file for which
the operation is inappropriate.


<dt>[ENXIO]<dd><index term="ENXIO, "></index>

No such device or address

Input or output on a special file refers to a device that does not exist,
or makes a request beyond the capabilities of the device. It may also occur
when, for example, a tape drive is not on-line.

<dt>[EOPNOTSUPP]<dd><index term="EOPNOTSUPP, "></index>

Operation not supported on socket

The type of socket (address family or protocol) does not support
the requested operation.

<dt>[EOVERFLOW]<dd><index term="EOVERFLOW, "></index>

Value too large to be stored in data type

The user ID or group ID of an IPC or file system
object was too large to be stored into appropriate member of the
caller-provided structure.  This error will only occur on implementations that
support a larger range of user ID or group ID values than the
declared structure member can support.  This usually occurs because
the IPC or file system object resides on a remote machine with a larger
value of the type <b>uid_t</b>, <b>off_t</b> or <b>gid_t</b> than the local
system.

<dt>[EPERM]<dd><index term="EPERM, "></index>

Operation not permitted

An attempt was made to perform an operation limited to processes with
appropriate privileges or to the owner of a file or other resource.

<dt>[EPIPE]<dd><index term="EPIPE, "></index>

Broken pipe

A write was attempted on a
&nbsp;socket,
&nbsp;pipe or FIFO for which there is no process to read the data.

<dt>[EPROTO]<dd><index term="EPROTO, "></index>

Protocol error

Some protocol error occurred.  This error is device specific, but is generally
not related to a hardware failure.

<dt>[EPROTONOSUPPORT]<dd><index term="EPROTONOSUPPORT, "></index>

Protocol not supported

The protocol is not supported by the address family, or
the protocol is not supported by the implementation.

<dt>[EPROTOTYPE]<dd><index term="EPROTOTYPE, "></index>

Socket type not supported

The socket type is not supported by the protocol.

<dt>[ERANGE]<dd><index term="ERANGE, "></index>

Result too large or too small

The result of the function is too large (overflow) or too small (underflow)
to be represented in the available space.
(Defined in the ISO&nbsp;C standard.)

<dt>[EROFS]<dd><index term="EROFS, "></index>

Read-only file system

An attempt was made to modify a file or directory on a file system that
is read only.

<dt>[ESPIPE]<dd><index term="ESPIPE, "></index>

Invalid seek

An attempt was made to access the file offset associated with a
pipe or FIFO.


<dt>[ESRCH]<dd><index term="ESRCH, "></index>

No such process

No process can be found corresponding to that specified by the given process
ID.

<dt>[ESTALE]<dd><index term="ESTALE, "></index>

Reserved

<dt>[ETIME]<dd><index term="ETIME, "></index>

STREAM
<i><a href="ioctl.html">ioctl()</a></i>
timeout

The timer set for a STREAMS
<i><a href="ioctl.html">ioctl()</a></i>
call has expired.  The cause of this error is device specific and could
indicate either a hardware or software failure, or a timeout value that is too
short for the specific operation.  The status of the
<i><a href="ioctl.html">ioctl()</a></i>
operation is indeterminate.

<dt>[ETIMEDOUT]<dd><index term="ETIMEDOUT, "></index>

Connection timed out

The connection to a remote machine has timed out.  If the connection timed out
during execution of the function that reported this error (as opposed to
timing out prior to the function being called), it is unspecified whether the
function has completed some or all of the documented behaviour associated with
a successful completion of the function.

<dt>[ETIMEDOUT]<dd><index term="ETIMEDOUT, "></index>

Operation timed out

The time limit associated with the operation was exceeded before the
operation completed.

<dt>[ETXTBSY]<dd><index term="ETXTBSY, "></index>

Text file busy

An attempt was made to execute a pure-procedure program that is currently
open for writing, or an attempt has been made to open for writing a
pure-procedure program that is being executed.

<dt>[EWOULDBLOCK]<dd><index term="EWOULDBLOCK, "></index>

Operation would block

An operation on a socket marked as non-blocking has encountered a
situation such as no data available that otherwise would have
caused the function to suspend execution.

An XSI-conforming implementation may assign the same values for
[EWOULDBLOCK] and [EAGAIN].

<dt>[EXDEV]<dd><index term="EXDEV, "></index>

Improper link

A link to a file on another file system was attempted.

</dl>
<h4><a name = "tag_000_004_001">&nbsp;</a>Additional Error Numbers</h4>
<xref type="3" name="adderr"></xref>
Additional implementation-dependent error numbers may be defined in
<i><a href="errno.h.html">&lt;errno.h&gt;</a></i>.
</blockquote><hr size=2 noshade>
<center><font size=2>
UNIX &reg; is a registered Trademark of The Open Group.<br>
Copyright &copy; 1997 The Open Group
<br> [ <a href="../index.html">Main Index</a> | <a href="../xshix.html">XSH</a> | <a href="../xcuix.html">XCU</a> | <a href="../xbdix.html">XBD</a> | <a href="../cursesix.html">XCURSES</a> | <a href="../xnsix.html">XNS</a> ]

</font></center><hr size=2 noshade>
</body></html>