.TH "Env Variables" 3 "Sun Nov 9 2014" "Version 4.15" "globus_xio" \" -*- nroff -*-
.ad l
.nh
.SH NAME
Env Variables \- 
The tcp driver uses the following environment variables
.IP "\(bu" 2
GLOBUS_HOSTNAME Used when setting the hostname in the contact string
.IP "\(bu" 2
GLOBUS_TCP_PORT_RANGE Used to restrict anonymous listener ports ex: GLOBUS_TCP_PORT_RANGE=4000,4100
.IP "\(bu" 2
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)
.IP "\(bu" 2
GLOBUS_TCP_SOURCE_RANGE Used to restrict local ports used in a connection
.IP "\(bu" 2
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
.IP "\(bu" 2
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\&. 
.PP

.SH "Author"
.PP 
Generated automatically by Doxygen for globus_xio from the source code\&.