Mono.Unix.Native.Errno Enumeration
Error values.

Syntax

public enum Errno

See Also

Stdlib.GetLastError
NativeConvert.FromErrno
NativeConvert.ToErrno

Remarks

Various error numbers that can be signaled by Mono.Unix.Native.Syscall methods. The most recent error can be retrieved from Stdlib.GetLastError.

The value of these members may not match the actual errno value used by your operating system. Use Mono.Unix.Native.NativeConvert to convert between the native errno value and an Mono.Unix.Native.Errno value.

Members

Member NameDescription
E2BIG Argument list too long. The number of bytes used for the argument and environment list of the new process exceeded the current limit of 65536 bytes (NCARGS in sys/param.h).
EACCES Permission denied. An attempt was made to access a file in a way forbidden by its file access permissions.
EADDRINUSE Address already in use. Only one usage of each address is normally permitted.
EADDRNOTAVAIL Cannot assign requested address. Normally results from an attempt to create a socket with an address not on this machine.
EADVDocumentation for this section has not yet been entered.
EAFNOSUPPORT Address family not supported by protocol family. An address incompatible with the requested protocol was used. For example, you shouldn’t necessarily expect to be able to use NS addresses with ARPA Internet protocols.
EAGAIN Resource temporarily unavailable. This is a temporary condition and later calls to the same routine may complete normally.
EALREADY Operation already in progress. An operation was attempted on a non-blocking object that already had an operation in progress.
EBADEDocumentation for this section has not yet been entered.
EBADF Bad file descriptor. A file descriptor argument was out of range, referred to no open file, or a read (write) request was made to a file that was only open for writing (reading).
EBADFD Bad file descriptor. A file descriptor argument was out of range, referred to no open file, or a read (write) request was made to a file that was only open for writing (reading).
EBADMSGDocumentation for this section has not yet been entered.
EBADRDocumentation for this section has not yet been entered.
EBADRQCDocumentation for this section has not yet been entered.
EBADSLTDocumentation for this section has not yet been entered.
EBFONTDocumentation for this section has not yet been entered.
EBUSY Device busy. An attempt to use a system resource which was in use at the time in a manner which would have conflicted with the request.
ECHILD No child processes. A Syscall.wait(2) or Syscall.waitpid(2) function was executed by a process that had no existing or unwaited-for child processes.
ECHRNGDocumentation for this section has not yet been entered.
ECOMMDocumentation for this section has not yet been entered.
ECONNABORTED Software caused connection abort. A connection abort was caused internal to your host machine.
ECONNREFUSED Connection refused. No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host.
ECONNRESET Connection reset by peer. A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a reboot.
EDEADLK Resource deadlock avoided. An attempt was made to lock a system resource that would have resulted in a deadlock situation
EDEADLOCKDocumentation for this section has not yet been entered.
EDESTADDRREQ Destination address required. A required address was omitted from an operation on a socket.
EDOM Numerical argument out of domain. A numerical input argument was outside the defined domain of the mathematical function.
EDOTDOTDocumentation for this section has not yet been entered.
EDQUOT Disc quota exceeded. A Syscall.write(2) to an ordinary file, the creation of a directory or symbolic link, or the creation of a directory entry failed because the user’s quota of disk blocks was exhausted, or the allocation of an inode for a newly created file failed because the user’s quota of inodes was exhausted.
EEXIST File exists. An existing file was mentioned in an inappropriate context, for instance, as the new link name in a Syscall.link(2) system call
EFAULT Bad address. The system detected an invalid address in attempting to use an argument of a call.
EFBIG File too large. The size of a file exceeded the maximum.
EHOSTDOWN Host is down. A socket operation failed because the destination host was down.
EHOSTUNREACH No route to host. A socket operation was attempted to an unreachable host.
EIDRM Identifier removed. An IPC identifier was removed while the current process was waiting on it.
EILSEQ Illegal byte sequence. While decoding a multibyte character the function came along an invalid or an incomplete sequence of bytes or the given wide character is invalid.
EINPROGRESS Operation now in progress. An operation that takes a long time to complete (such as a Syscall.connect(2)) was attempted on a non-blocking object (see Syscall.fcntl(2)).
EINTR Interrupted system call. An asynchronous signal (such as Signum.SIGINT or Signum.SIGQUIT) was caught by the process during the execution of an interruptible function. If the signal handler performs a normal return, the interrupted system call will seem to have returned the error condition.
EINVAL Invalid argument. Some invalid argument was supplied. (For example, specifying an undefined signal to a Stdlib.signal(3) function or a Syscall.kill(2) system call).
EIO Input/output error. Some physical input or output error occurred. This error will not be reported until a subsequent operation on the same file descriptor and may be lost (over written) by any subsequent errors.
EISCONN Socket is already connected. A Syscall.connect(2) request was made on an already connected socket; or, a Syscall.sendto(2) or Syscall.sendmsg(2) request on a connected socket specified a destination when already connected.
EISDIR Is a directory. An attempt was made to open a directory with write mode specified.
EISNAMDocumentation for this section has not yet been entered.
EL2HLTDocumentation for this section has not yet been entered.
EL2NSYNCDocumentation for this section has not yet been entered.
EL3HLTDocumentation for this section has not yet been entered.
EL3RSTDocumentation for this section has not yet been entered.
ELIBACCDocumentation for this section has not yet been entered.
ELIBBADDocumentation for this section has not yet been entered.
ELIBEXECDocumentation for this section has not yet been entered.
ELIBMAXDocumentation for this section has not yet been entered.
ELIBSCNDocumentation for this section has not yet been entered.
ELNRNGDocumentation for this section has not yet been entered.
ELOOP Too many levels of symbolic links. A path name lookup involved more than 32 (MAXSYMLINKS) symbolic links
EMEDIUMTYPEDocumentation for this section has not yet been entered.
EMFILE Too many open files.
Too many links. Maximum allowable hard links to a single file has been exceeded.
EMSGSIZE Message too long. A message sent on a socket was larger than the internal message buffer or some other network limit.
EMULTIHOPDocumentation for this section has not yet been entered.
ENAMETOOLONG File name too long. A component of a path name exceeded {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} characters. (See also the description of PathConf._PC_NO_TRUNC in Syscall.pathconf(2).)
ENAVAILDocumentation for this section has not yet been entered.
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 Too many open files in system. Maximum number of file descriptors allowable on the system has been reached and a requests for an open cannot be satisfied until at least one has been closed.
ENOANODocumentation for this section has not yet been entered.
ENOBUFS No buffer space available. An operation on a socket or pipe was not performed because the system lacked sufficient buffer space or because a queue was full.
ENOCSIDocumentation for this section has not yet been entered.
ENODATADocumentation for this section has not yet been entered.
ENODEV Operation not supported by 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.
ENOENT No such file or directory. A component of a specified pathname did not exist, or the pathname was an empty string.
ENOEXEC Exec format error. A request was made to execute a file that, although it has the appropriate permissions, was not in the format required for an executable file.
ENOLCK No locks available. A system-imposed limit on the number of simultaneous file locks was reached.
No locks available. A system-imposed limit on the number of simultaneous file locks was reached.
ENOMEDIUMDocumentation for this section has not yet been entered.
ENOMEM Cannot allocate memory. The new process image required more memory than was allowed by the hardware or by system-imposed memory management constraints. A lack of swap space is normally temporary; however, a lack of core is not. Soft limits may be increased to their corresponding hard limits.
ENOMSG No message of desired type. An IPC message queue does not contain a message of the desired type, or a message catalog does not contain the requested message.
ENONETDocumentation for this section has not yet been entered.
ENOPKGDocumentation for this section has not yet been entered.
ENOPROTOOPT Prootocol not available. A bad option or level was specified in a Syscall.getsockopt(2) or Syscall.setsockopt(2) call.
ENOSPC No space left on device. A Syscall.write(2) to an ordinary file, the creation of a directory or symbolic link, or the creation of a directory entry failed because no more disk blocks were available on the file system, or the allocation of an inode for a newly created file failed because no more inodes were available on the file system.
ENOSRDocumentation for this section has not yet been entered.
ENOSTRDocumentation for this section has not yet been entered.
ENOSYS Function not implemented. Attempted a system call that is not available on this system.
ENOTBLK Block device required. A block device operation was attempted on a non-block device or file.
ENOTCONN Socket is not connected. An request to send or receive data was disallowed because the socket was not connected and (when sending on a datagram socket) no address was supplied.
ENOTDIR Not a directory. A component of the specified pathname existed, but it was not a directory, when a directory was expected.
ENOTEMPTY Directory not empty. A directory with entries other than ‘.’ and ‘..’ was supplied to a remove directory or rename call.
ENOTNAMDocumentation for this section has not yet been entered.
ENOTSOCK Socket operation on non-socket. Self-explanatory
ENOTTY Inappropriate ioctl for device. A control function (see Syscall.ioctl(2)) was attempted for a file or special device for which the operation was inappropriate.
ENOTUNIQDocumentation for this section has not yet been entered.
ENXIO Device not configured. Input or output on a special file referred to a device that did not exist, or made a request beyond the limits of the device. This error may also occur when, for example, a tape drive is not online or no disk pack is loaded on a drive.
EOPNOTSUPP Operation not supported. The attempted operation is not supported for the type of object referenced. Usually this occurs when a file descriptor refers to a file or socket that cannot support this operation, for example, trying to accept a connection on a datagram socket.
EOVERFLOW Value too large to be stored in data type. A numerical result of the function was too large to be stored in the caller provided space.
EPERM 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 resources.
EPFNOSUPPORT Protocol family not supported. The protocol family has not been configured into the system or no implementation for it exists.
EPIPE Broken pipe. A write on a pipe, socket or FIFO for which there is no process to read the data.
EPROTODocumentation for this section has not yet been entered.
EPROTONOSUPPORT Protocol not supported. The protocol has not been configured into the system or no implementation for it exists.
EPROTOTYPE Protocol wrong type for socket. A protocol was specified that does not support the semantics of the socket type requested. For example, you cannot use the ARPA Internet UDP protocol with type SOCK_STREAM.
ERANGE Result too large. A numerical result of the function was too large to fit in the available space (perhaps exceeded precision)
EREMCHGDocumentation for this section has not yet been entered.
EREMOTEDocumentation for this section has not yet been entered.
EREMOTEIODocumentation for this section has not yet been entered.
ERESTARTDocumentation for this section has not yet been entered.
EROFS Read-only file system. An attempt was made to modify a file or directory on a file system that was read-only at the time.
ESHUTDOWN Cannot send after socket shutdown. A request to send data was disallowed because the socket had already been shut down with a previous Syscall.shutdown(2) 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.
ESPIPE Illegal seek. An Syscall.lseek(2) system call was issued on a socket, pipe or FIFO.
ESRCH No such process. No process could be found corresponding to that specified by the given process ID.
ESRMNTDocumentation for this section has not yet been entered.
ESTALE Stale NFS file handle. An attempt was made to access an open file (on an NFS file system) which is now unavailable as referenced by the file descriptor. This may indicate the file was deleted on the NFS server or some other catastrophic event occurred.
ESTRPIPEDocumentation for this section has not yet been entered.
ETIMEDocumentation for this section has not yet been entered.
ETIMEDOUT Operation timed out. A Syscall.connect(2) or Syscall.send(2) request failed because the connected party did not properly respond after a period of time. (The timeout period is dependent on the communication protocol.)
ETOOMANYREFSDocumentation for this section has not yet been entered.
ETXTBSY Text file busy. The new process was a pure procedure (shared text) file which was open for writing by another process, or while the pure procedure file was being executed an Syscall.open(2) call requested write access.
EUCLEANDocumentation for this section has not yet been entered.
EUNATCHDocumentation for this section has not yet been entered.
EUSERS Too many users. The quota system ran out of table entries.
EWOULDBLOCKDocumentation for this section has not yet been entered.
EXDEV Cross-device link. A hard link to a file on another file system was attempted.
EXFULLDocumentation for this section has not yet been entered.

Requirements

Namespace: Mono.Unix.Native
Assembly: Mono.Posix (in Mono.Posix.dll)
Assembly Versions: 1.0.5000.0, 2.0.0.0, 4.0.0.0