.IX \f4errnos\fP(D5DK)

NAME

errnos − error numbers

SYNOPSIS

#include <sys/errno.h>

DESCRIPTION

The following is a list of the error codes that drivers may return from their entry points, or include in STREAMS messages (for example, M_ERROR messages). 

EACCESPermission denied.  An attempt was made to access a file in a way forbidden by its file access permissions. 

EADDRINUSEThe address requested is already in use. 

EADDRNOTAVAILThe address requested cannot be assigned. 

EAFNOSUPPORTThe address family specified is not installed or supported on the host. 

EAGAINTemporary resource allocation failure; try again later.  Drivers can return this error when resource allocation fails, for example, kmem_alloc(D3DK) or allocb(D3DK). 

EALREADYThe operation requested is already being performed. 

EBUSYDevice is busy.  This can be used for devices that require exclusive access. 

ECONNABORTEDA received connect request was aborted when the peer closed its endpoint. 

ECONNREFUSEDThe connection was refused. 

ECONNRESETThe connection was reset by the peer entity. 

EDESTADDRREQThe requested operation required a destination address but none was supplied. 

EFAULTBad address.  Drivers should return this error whenever a call to copyin(D3DK) or copyout(D3DK) fails. 

EHOSTDOWNHost is down. 

EHOSTUNREACHNo route to host. 

EINPROGRESSThe operation requested is now in progress. 

EINTRInterrupted operation.  Drivers can return this error whenever an interruptible operation is interrupted by receipt of an asynchronous signal. 

EINVALInvalid argument.  Drivers can return this error for operations that have invalid parameters specified. 

EIOAn I/O error has occurred.  Drivers can return this error when an input or output request has failed. 

EISCONNThe endpoint is already connected. 

EMSGSIZEMessage too long. The protocol is such that there is a limit to the size of a message and that limit has been exceeded. 

ENETDOWNThe network trying to be reached is down. 

ENETRESETThe network dropped the connection because of a reset. 

ENETUNREACHThe network trying to be reached is unreachable. 

ENOBUFSNo buffer space available. 

ENODEVNo such device.  Drivers can return this error when an attempt is made to apply an inappropriate function to a device; for example, trying to write a write-protected medium. 

ENOMEMNot enough memory.  Drivers can return this error when resource allocation fails and it is either inconvenient or impossible for a retry to occur. 

ENOPROTOOPTThe protocol option requested is not available at the level indicated. 

ENOSPCThe device is out of free space. 

ENOTCONNThe requested operation requires the endpoint to be connected but it is not. 

ENXIONo such device or address.  Drivers can return this error when trying to open an invalid minor device, or when trying to perform I/O past the end of a device. 

EOPNOTSUPPThe operation requested is not supported. 

EPERMPermission denied.  Drivers can return this error when the current process doesn’t have sufficient privilege for the operation attempted. 

EPROTOProtocol error.  Drivers can return this error when they incur a protocol error, such as not being able to generate the proper protocol message because of resource exhaustion, and not being able to recover gracefully. 

EROFSAn attempt was made to open for writing a read-only device. 

ETIMEDOUTThe connection timed out. 

NOTES

The above examples are not exhaustive. 

SEE ALSO

bioerror(D3DK), geterror(D3DK)

DDI/DKI