02.03.2014 Views

Tornado

Tornado

Tornado

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

C<br />

<strong>Tornado</strong> Tools Reference<br />

-use_portmapper<br />

Use the local portmapper to register the target server rpc services. This flag MUST be<br />

set if tornado tools version 1.x have to connect to this target server.<br />

-u fileName | -users fileName<br />

Specify a file containing a list of authorized users. Only users whose IDs appear as<br />

lines in this file will be able to connect tools to the target server, unless the file<br />

contains the character + on a line by itself (which authorizes all users).<br />

-V | -Verbose<br />

Turn on the target server’s verbose mode. By default, the target server is silent. In<br />

verbose mode, it displays information, warning and error messages on the standard<br />

output.<br />

-v | -version<br />

Identify the version of the target server.<br />

-Wd fileName | -Wdebug fileName<br />

Log every WTX request sent to the target server in the specified file. If the file exists,<br />

log messages will be appended to it (unless the -Wm flag is set).<br />

-Wf request | -Wfilter request<br />

Remove WTX request from the WTX log file. The default WTX log behavior is to log<br />

every requests the target server is servicing. This may lead to a huge file. This flag<br />

allows to reduce the amount of information by giving a regular expression to filter<br />

out WTX requests.<br />

-Wm size | -Wmax size<br />

Max size in bytes for the WTX logging file. If this flag is set, the file size will be<br />

limited to the given value, and written as a circular file: i.e. when this value is<br />

reached, the file is rewritten from the beginning. If the file exists, it will be erased. So,<br />

be aware that if the target server restarts (due to a target reboot, for example), the<br />

WTX log file will be reset.<br />

C<br />

EXAMPLES<br />

Start a target server on target with IP address equal to “147.108.108.1” in verbose mode<br />

and give it the name “myTargetServer”.<br />

tgtsvr -V -name myTargetServer 147.108.108.1<br />

Display the flags handled by the wdbpipe backend.<br />

tgtsvr -h -B wdbpipe<br />

Start a target server named “myTargetServer” on VxWorks simulator number “0” with<br />

WDB request log going to file “/tmp/vxsim0Wdb.log”<br />

tgtsvr -B wdbpipe -Bd /tmp/vxsim0Wdb.log vxsim0 -n myTargetServer<br />

Specify a core file to the target server attached to a serial line on COM2 at 38400 bauds<br />

(Windows). Note that the target name flag can be anything in this case it is only used to<br />

build the target server name.<br />

363

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!