xsh_chap02_03.html

IEEE 1003.1-2003, Single Unix Specification v3

<dd>
Message too large. A message sent on a transport provider was larger than an internal message buffer or some other network limit. 

<p>or:</p>

<p>Inappropriate message buffer length.</p>
</dd>

<dt>[EMULTIHOP]</dt>

<dd>
Reserved.</dd>

<dt>[ENAMETOOLONG]</dt>

<dd>
Filename too long. The length of a pathname exceeds {PATH_MAX}, or a pathname component is longer than {NAME_MAX}. This error may
also occur when pathname substitution, as a result of encountering a symbolic link during pathname resolution, results in a
pathname string the size of which exceeds {PATH_MAX}.</dd>

<dt>[ENETDOWN]</dt>

<dd>
Network is down. The local network interface used to reach the destination is down.</dd>

<dt>[ENETRESET]</dt>

<dd>
The connection was aborted by the network.</dd>

<dt>[ENETUNREACH]</dt>

<dd>
Network unreachable. No route to the network is present.</dd>

<dt>[ENFILE]</dt>

<dd>
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.</dd>

<dt>[ENOBUFS]</dt>

<dd>
No buffer space available. Insufficient buffer resources were available in the system to perform the socket operation.</dd>

<dt>[ENODATA]</dt>

<dd><sup>[<a href="javascript:open_code('XSR')">XSR</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
"0"><br>
No message available. No message is available on the STREAM head read queue. <img src="../images/opt-end.gif" alt="[Option End]"
border="0"></dd>

<dt>[ENODEV]</dt>

<dd>
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.</dd>

<dt>[ENOENT]</dt>

<dd>
No such file or directory. A component of a specified pathname does not exist, or the pathname is an empty string.</dd>

<dt>[ENOEXEC]</dt>

<dd>
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.</dd>

<dt>[ENOLCK]</dt>

<dd>
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.</dd>

<dt>[ENOLINK]</dt>

<dd>
Reserved.</dd>

<dt>[ENOMEM]</dt>

<dd>
Not enough space. The new process image requires more memory than is allowed by the hardware or system-imposed memory management
constraints.</dd>

<dt>[ENOMSG]</dt>

<dd>
No message of the desired type. The message queue does not contain a message of the required type during XSI interprocess
communication.</dd>

<dt>[ENOPROTOOPT]</dt>

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

<dt>[ENOSPC]</dt>

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

<dt>[ENOSR]</dt>

<dd><sup>[<a href="javascript:open_code('XSR')">XSR</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
"0"><br>
No STREAM resources. Insufficient STREAMS memory resources are available to perform a STREAMS-related function. This is a temporary
condition; it may be recovered from if other processes release resources. <img src="../images/opt-end.gif" alt="[Option End]"
border="0"></dd>

<dt>[ENOSTR]</dt>

<dd><sup>[<a href="javascript:open_code('XSR')">XSR</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
"0"><br>
Not a STREAM. A STREAM function was attempted on a file descriptor that was not associated with a STREAMS device. <img src=
"../images/opt-end.gif" alt="[Option End]" border="0"></dd>

<dt>[ENOSYS]</dt>

<dd>
Function not implemented. An attempt was made to use a function that is not available in this implementation.</dd>

<dt>[ENOTCONN]</dt>

<dd>
Socket not connected. The socket is not connected.</dd>

<dt>[ENOTDIR]</dt>

<dd>
Not a directory. A component of the specified pathname exists, but it is not a directory, when a directory was expected.</dd>

<dt>[ENOTEMPTY]</dt>

<dd>
Directory not empty. A directory other than an empty directory was supplied when an empty directory was expected.</dd>

<dt>[ENOTSOCK]</dt>

<dd>
Not a socket. The file descriptor does not refer to a socket.</dd>

<dt>[ENOTSUP]</dt>

<dd>
Not supported. The implementation does not support this feature of the Realtime Option Group.</dd>

<dt>[ENOTTY]</dt>

<dd>
Inappropriate I/O control operation. A control function has been attempted for a file or special file for which the operation is
inappropriate.</dd>

<dt>[ENXIO]</dt>

<dd>
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.</dd>

<dt>[EOPNOTSUPP]</dt>

<dd>
Operation not supported on socket. The type of socket (address family or protocol) does not support the requested operation.</dd>

<dt>[EOVERFLOW]</dt>

<dd>
Value too large to be stored in data type. An operation was attempted which would generate a value that is outside the range of
values that can be represented in the relevant data type or that are allowed for a given data item.</dd>

<dt>[EPERM]</dt>

<dd>
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.</dd>

<dt>[EPIPE]</dt>

<dd>
Broken pipe. A write was attempted on a socket, pipe, or FIFO for which there is no process to read the data.</dd>

<dt>[EPROTO]</dt>

<dd>
Protocol error. Some protocol error occurred. This error is device-specific, but is generally not related to a hardware
failure.</dd>

<dt>[EPROTONOSUPPORT]</dt>

<dd>
Protocol not supported. The protocol is not supported by the address family, or the protocol is not supported by the
implementation.</dd>

<dt>[EPROTOTYPE]</dt>

<dd>
Protocol wrong type for socket. The socket type is not supported by the protocol.</dd>

<dt>[ERANGE]</dt>

<dd>
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).</dd>

<dt>[EROFS]</dt>

<dd>
Read-only file system. An attempt was made to modify a file or directory on a file system that is read-only.</dd>

<dt>[ESPIPE]</dt>

<dd>
Invalid seek. An attempt was made to access the file offset associated with a pipe or FIFO.</dd>

<dt>[ESRCH]</dt>

<dd>
No such process. No process can be found corresponding to that specified by the given process ID.</dd>

<dt>[ESTALE]</dt>

<dd>
Reserved.</dd>

<dt>[ETIME]</dt>

<dd><sup>[<a href="javascript:open_code('XSR')">XSR</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
"0"><br>
STREAM <a href="../functions/ioctl.html"><i>ioctl</i>()</a> timeout. The timer set for a STREAMS <a href=
"../functions/ioctl.html"><i>ioctl</i>()</a> 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 <a href=
"../functions/ioctl.html"><i>ioctl</i>()</a> operation is unspecified. <img src="../images/opt-end.gif" alt="[Option End]" border=
"0"></dd>

<dt>[ETIMEDOUT]</dt>

<dd>
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 behavior associated with a successful completion of the function. 

<p>or:</p>

<p>Operation timed out. The time limit associated with the operation was exceeded before the operation completed.</p>
</dd>

<dt>[ETXTBSY]</dt>

<dd>
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.</dd>

<dt>[EWOULDBLOCK]</dt>

<dd>
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. 

<p>A conforming implementation may assign the same values for [EWOULDBLOCK] and [EAGAIN].</p>
</dd>

<dt>[EXDEV]</dt>

<dd>
Improper link. A link to a file on another file system was attempted.</dd>
</dl>

<h4><a name="tag_02_03_01"></a>Additional Error Numbers</h4>

<p>Additional implementation-defined error numbers may be defined in <a href=
"../basedefs/errno.h.html"><i>&lt;errno.h&gt;</i></a>.</p>



<hr size="2" noshade>
<center><font size="2"><!--footer start-->
UNIX &reg; is a registered Trademark of The Open Group.<br>
POSIX &reg; is a registered Trademark of The IEEE.<br>
[ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
"../utilities/contents.html">XCU</a> | <a href="../functions/contents.html">XSH</a> | <a href="../xrat/contents.html">XRAT</a>
]</font></center>

<!--footer end-->
<hr size="2" noshade>
</body>
</html>