.TH "globus_xio_udp_driver_errors" 3 "Wed Feb 27 2019" "Version 6.1" "globus_xio" \" -*- nroff -*-
.ad l
.nh
.SH NAME
globus_xio_udp_driver_errors \- Error Types\&.  

.SH SYNOPSIS
.br
.PP
.SS "Enumerations"

.in +1c
.ti -1c
.RI "enum \fBglobus_xio_udp_error_type_t\fP { \fBGLOBUS_XIO_UDP_ERROR_NO_ADDRS\fP, \fBGLOBUS_XIO_UDP_ERROR_SHORT_WRITE\fP }"
.br
.in -1c
.SH "Detailed Description"
.PP 
Error Types\&. 

The UDP driver is very close to the system code, so most errors reported by it are converted from the system errno\&. A few of the exceptions are GLOBUS_XIO_ERROR_COMMAND, GLOBUS_XIO_ERROR_CONTACT_STRING, GLOBUS_XIO_ERROR_CANCELED, \fBGLOBUS_XIO_UDP_ERROR_NO_ADDRS\fP, and \fBGLOBUS_XIO_UDP_ERROR_SHORT_WRITE\fP
.PP
\fBSee also:\fP
.RS 4
globus_xio_driver_error_match() 
.PP
globus_error_errno_match() 
.RE
.PP

.SH "Enumeration Type Documentation"
.PP 
.SS "enum \fBglobus_xio_udp_error_type_t\fP"
UDP driver specific error types 
.PP
\fBEnumerator\fP
.in +1c
.TP
\fB\fIGLOBUS_XIO_UDP_ERROR_NO_ADDRS \fP\fP
Indicates that no IPv4/6 compatible sockets could be resolved for the specified hostname 
.TP
\fB\fIGLOBUS_XIO_UDP_ERROR_SHORT_WRITE \fP\fP
Indicates that a write of the full buffer failed\&. Possibly need to increase the send buffer size\&. 
.SH "Author"
.PP 
Generated automatically by Doxygen for globus_xio from the source code\&.