3.3

D Environment Variables
256
d. Click OK to save the setting and close the dialog box.
8. Close the Registry Editor window.
Environmental Variables for Servers
You can control some of the behavior of rxnet by putting some enviroment variable settings
in the /site/env/rxnet file.
n
If the /site/env/rxnet file or its parent directory /site/env do not exist you need to create the
directory using the mkdir /site/env command, before you can edit the file. Contact Avid if you
need assistance with this procedure.
The specific variables are:
RXDEBUG=<level>
An rxdebug level of 2 produces the command traffic to/from rxnet.
RXDEBUGFILE=<filename>
The RXDEBUGFILE file allows you to cause rxnet diagnostics to be put into
<filename>.<process id> instead of the console.
RX_HOT_TO_GO=0
When RX_HOT_TO_GO=0 is set in /site/env/rxnet, then rxnet will not print Hot-To-Go
diagnostics.
RXSITELISTSZ=<size>
The list size controls the number of stories included in a queue list when rxnet responds to
an FTP list command. The default value for this is 300.
RXSITEFORMAT=<format>
The format controls which transfer protocol is initially used. This can be set to NSML or
SEP. The default is NSML. This is how you get a foreign application, such as CNN which
operates in SEP but did not use the FTP SITE command to change the format to SEP.
RXSEPFIELDLIST=<filename>
RXSEPFIELDLIST defines a file name. That file is processed as a list of field substitutions.
For instance,
RXSEPFIELDLIST=/site/env/substitutes in the /site/env/rxnet file, rxnet
inherits this variable when invoked.