errno.2 (2010 09)

e
errno(2) errno(2)
[EMLINK] Too many links. An attempt to make more than the maximum number of links to a file.
[EMSGSIZE] Message too long. The socket requires that the message be sent atomically, and the size
of the message to be sent made this impossible.
[ENAMETOOLONG]
File name too long. A path specified exceeds the maximum path length for the system.
The maximum path length is specified by
PATH_MAX and is defined in <limits.h>.
PATH_MAX is guaranteed to be at least 1023 bytes. This error is also generated if the
length of a path name component exceeds
NAME_MAX
and the _POSIX_NO_TRUNC
option is in effect for the specified path. Currently,
_POSIX_NO_TRUNC
is in effect only
for HFS file systems configured to allow path name components up to 255 bytes long (see
convertfs (1M)) and therefore only path names referring to such file systems can generate
the error for this case. The values of
NAME_MAX, PATH_MAX, and _POSIX_NO_TRUNC
for a particular path name can be queried by using the
pathconf() system call (see
pathconf (2)).
[ENETDOWN] Network is down. A socket operation encountered a dead network.
[ENETRESET] Network dropped connection on reset. The host you were connected to crashed and
rebooted.
[ENETUNREACH]
Network is unreachable. A socket operation was attempted to an unreachable network.
[ENFILE] File table overflow. The system’s table of open files is full, and temporarily no more
open()s can be accepted.
[ENOBUFS] No buffer space available. An operation on a socket was not performed because the sys-
tem lacked sufficient buffer space.
[ENODEV] No such device. An attempt was made to apply an inappropriate system call to a device
(such as read a write-only device).
[ENOENT] No such file or directory. This error occurs when a file name is specified and the file
should exist but does not, or when one of the directories in a path name does not exist. It
also occurs with
msgget(), semget(), and shmget() when key does not refer to any
object and the IPC_CREAT flag is not set.
[ENOEXEC] Exec format error. A request is made to execute a file which, although it has the
appropriate permissions, does not start with a valid magic number (see a.out (4)), or the
file is too small to have a valid executable file header.
[ENOLCK] System lock table is full. Too many files have file locks on them, or there are too many
record locks on files, or there are too many instances of a reading or writing process
sleeping until an enforcement mode lock clears. This error may also indicate system
problems in handling a lock request on a remote NFS file. This error is also currently
returned for all attempts to perform locking operations on a remote NFS file that has its
locking enforcement mode bit set, since the stateless nature of NFS prevents maintaining
the necessary lock information.
[ENOLINK] No connection. The link with the device has been severed or disconnected.
[ENOMEM] Not enough space. During a system call such as
exec(), brk(), fork(),orsbrk(),
a program asks for more space than the system is able to supply. This may not be a tem-
porary condition; the maximum space size is a system parameter. The error can also
occur if there is not enough swap space during a fork().
[ENOMSG] No message of desired type. An attempt was made to receive a message of a type that
does not exist on the specified message queue; see msgop(2).
[ENOPROTOOPT]
Protocol option not available. This may be returned for a
getsockopt() or set-
sockopt() call (see getsockopt (2)) if the user specified an option that the local system
does not support or for any system call that causes the local system to send a network
protocol option that a remote system does not support, including a system call that
operates on an NFS file.
[ENOSPC] No space left on device. During a
write() to an ordinary file, there is no free space
left on the device; or no space in system table during msgget(), semget(),or
semop() while SEM_UNDO flag is set.
HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3