---
name: "tcp_driver_envs"
section: "3"
platform: "linux"
package: "libglobus-xio-doc"
version: "3.3-1"
release: "Debian 7 (Wheezy)"
platforms: ["linux"]
url: "https://new.carta.tech/tcp_driver_envs"
---

# tcp\_driver\_envs(3)

The tcp driver uses the following environment variables.

## NAME

Env Variables - The tcp driver uses the following environment variables.

- •

  GLOBUS\_HOSTNAME Used when setting the hostname in the contact string

- •

  GLOBUS\_TCP\_PORT\_RANGE Used to restrict anonymous listener ports ex: GLOBUS\_TCP\_PORT\_RANGE=4000,4100

- •

  GLOBUS\_TCP\_PORT\_RANGE\_STATE\_FILE Used in conjunction with GLOBUS\_TCP\_PORT\_RANGE to maintain last used port among many applications making use of the same port range. That last port + 1 will be used as a starting point within the specified tcp port range instead of always starting at the beginning. This is really only necessary when a machine is behind a stateful firewall which is holding a port in a different state than the application's machine. See bugzilla.globus.org, bug 1851 for more info. ex: GLOBUS\_TCP\_PORT\_RANGE\_STATE\_FILE=/tmp/port\_state (file will be created if it does not exist)

- •

  GLOBUS\_TCP\_SOURCE\_RANGE Used to restrict local ports used in a connection

- •

  GLOBUS\_XIO\_TCP\_DEBUG Available if using a debug build. See globus\_debug.h for format. The TCP driver defines the levels TRACE for all function call tracing and INFO for write buffer sizes

- •

  GLOBUS\_XIO\_SYSTEM\_DEBUG Available if using a debug build. See globus\_debug.h for format. The TCP driver uses globus\_xio\_system (along with the File and UDP drivers) which defines the following 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 actually read or written. This can contain binary data, so be careful when you enable it.

## Author

Generated automatically by Doxygen for globus xio from the source code.