GLOBUS_XIO_FILE_DRIVER_ENVS(3)

πŸ“¦
version 6.6 Β· 4 versions
, in debian trixie, epel 10, fedora 43, fedora 44, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– globus_xio_file_driver_envs β€” Environment Variables πŸ’–

okay bestie, this is the globus_xio_file_driver_envs page from the globus_xio library functions manual, and it's literally all about environment variables. no cap. 🫢


✨ SYNOPSIS ✨

πŸ“– Detailed Description

Environment variables. that's it, that's the whole vibe. πŸ’…


🌸 DESCRIPTION 🌸

so the file driver is lowkey tuned by some environment variables, and here's the full list because we do not gatekeep:

  • GLOBUS_XIO_FILE_DEBUG β€” only available if you're running a debug build. for the format, go look at globus_debug.h. the File driver defines these levels: TRACE, which traces all function calls, and INFO, which is about write buffer sizes. πŸ‘‘
  • GLOBUS_XIO_SYSTEM_DEBUG β€” also only available if you're running a debug build, and again, peep globus_debug.h for the format. the File driver uses globus_xio_system (and so do the TCP and UDP drivers, bestie, they're all in this together), which defines these levels: TRACE for all function call tracing, DATA for data read and written counts, INFO for some special events, and RAW which dumps the raw buffers that actually got read or written.
⚠️ okay real talk about that RAW one: it can contain binary data, so be careful when you enable it. like, genuinely careful. that's not a drill. πŸ’€

πŸ’œ Author

Generated automatically by Doxygen for globus_xio from the source code. (not me writing my own bio, the robots did this one 🧚)


and that's the whole page, bestie β€” you ate it. this was globus_xio, Version 6.6, and the page was globus_xio...driver_envs(3). mwah, go forth and debug responsibly. πŸŽ€βœ¨πŸ¦‹