errno.2 (2010 09)

e
errno(2) errno(2)
[ENOSYM] Symbol does not exist in executable. The dynamic loader was unable to resolve a sym-
bolic reference in a shared library during a call to one of the dynamic loader interface
routines (see shl_load (3X). The program may be in an inconsistent state and should be
terminated immediately.
[ENOSYS] Function is not available. The requested function or operation is not implemented or not
configured in the system.
[ENOTBLK] Block device required. A nonblock file was mentioned where a block device was required,
such as in
mount().
[ENOTCONN] Socket is not connected. A request to send or receive data was disallowed because the
socket was not connected.
[ENOTDIR] Not a directory. A nondirectory was specified where a directory is required, such as in a
path prefix or as an argument to
chdir().
[ENOTEMPTY]
Directory not empty. An attempt was made to remove a nonempty directory.
[ENOTSOCK] Socket operation on nonsocket. An operation was attempted on something that is not a
socket.
[ENOTTY] Not a typewriter. The (
ioctl()) command is inappropriate to the selected device type.
[ENXIO] No such device or address. I/O on a special file refers to a subdevice that does not exist,
or is beyond the limits of the device. It can also occur when, for example, a tape drive is
not on line or no disk pack is loaded on a drive.
[EOPNOTSUPP]
Operation not supported. The requested operation on a socket or NFS file is either
invalid or unsupported. For example, this might occur when an attempt to
accept() a
connection on a datagram socket fails.
[EPERM] Not owner. Typically, this error indicates an attempt to modify a file in some way forbid-
den except to its owner or the superuser, such as to change its mode. It is also returned
for attempts by ordinary users to do things for which they need, but lack, a special
privilege.
[EPFNOSUPPORT]
Protocol family not supported. The protocol family has not been configured into the sys-
tem or no implementation for it exists. The socket is not connected.
[EPIPE] Broken pipe. Data has been written to a pipe for which the other (reading) end has been
closed. This most often occurs when the reading process exits before the writing process.
This condition also generates the signal
SIGPIPE; the error is returned if the signal is
ignored.
[EPROTONOSUPPORT]
Protocol not supported. The protocol has not been configured into the system or no imple-
mentation for it exists.
[EPROTOTYPE]
Protocol wrong type for socket. A protocol was specified that does not support the seman-
tics of the socket type requested. For example, ARPA Internet UDP protocol cannot be
used with type
SOCK_STREAM.
[ERANGE] Result too large. The value of a function in the math package (3M) is not representable
within machine precision, or a
semop() call would cause either a semaphore value or a
semaphore adjust value to exceed it system-imposed maximum.
[EROFS] Read-only file system. An attempt to modify a file or directory was made on a device
mounted read-only.
[ESHUTDOWN]
Cannot send after socket shutdown. A request to send data was disallowed because the
socket had already been shut down with a previous
shutdown() call.
[ESOCKTNOSUPPORT]
Socket type not supported. The support for the socket type has not been configured into
the system or no implementation for it exists.
4 Hewlett-Packard Company − 4 − HP-UX 11i Version 3: September 2010