globus_xio...ver_errors(3)

💖 NAME 💖

globus_xio_tcp_driver_errors — bestie, it's literally just Error Types. That's the whole vibe. Errors. Types. 💅

Also hi, you're reading the globus_xio...ver_errors(3) page from the Library Functions Manual, so like… you're in the right place, queen. 🫶

---

✨ SYNOPSIS ✨

Enumerations

enum globus_xio_tcp_error_type_t { GLOBUS_XIO_TCP_ERROR_NO_ADDRS }

okay so that's the enum, that's the one value, we move. 🦋

---

🌸 Detailed Description 🌸

Error Types. (Yes, again. It's giving "the title is the description" and honestly? iconic.)

The TCP driver is super duper close to the system code, so most of the errors it reports are just converted straight from the system errno. No cap. It's basically a translator between your kernel's feelings and the Globus XIO error system. 😭

A few of the exceptions to that — the ones that are not just errno in a cute outfit — are:

• GLOBUS_XIO_ERROR_EOF
• GLOBUS_XIO_ERROR_COMMAND
• GLOBUS_XIO_ERROR_CONTACT_STRING
• GLOBUS_XIO_ERROR_CANCELED
• GLOBUS_XIO_TCP_ERROR_NO_ADDRS

See also

• globus_xio_driver_error_match()
• globus_error_errno_match()

like, if you wanna match errors, those two are your girls. 💜

---

👑 Enumeration Type Documentation 👑

enum globus_xio_tcp_error_type_t

TCP driver specific error types. It's giving "custom errors, but make it TCP." 🎀

Enumerator

• GLOBUS_XIO_TCP_ERROR_NO_ADDRS — this one means no IPv4/6 compatible sockets could be resolved for the specified hostname. Like, you asked for a host, and the resolver was like "girl, who? never heard of her." 💀 No compatible sockets found, periodt.

---

🧚 Author 🧚

Generated automatically by Doxygen for globus_xio from the source code. So nobody hand-wrote this, it's a robot doing its little robot thing and we respect it. 🤖✨

---

And that's the whole page, bestie! This was the globus_xio documentation, Version 6.6, and the footer is basically the same thing but make it official. Slay, bye, go resolve some sockets responsibly. 🌈🫶💖