c-tools2.html

vxworks相关论文

<dd><div class="Indent"><a name="90933"> </a>Make the TSFS read-only (recommended for most purposes).</div>
<br>
</dl>

<dd><div class="Item"><a name="90934"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Read / Write</font></b> </div>
<dl class="margin">

<dd><div class="Indent"><a name="90935"> </a>Allow read and write access to host files by target processes using the TSFS. When this option is specified, access to the target server is restricted to processes running under the same user ID as the server. </div>
<br>
</dl>

</dl>

</dl>
<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="90945">Console and Redirection</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="90949"> </a>Tornado supports virtual I/O to the host from target applications (see <a href="c-overview5.html#84294"><i class="title">Virtual I/O</i></a>). By default, any virtual output from the target is broadcast to all shell windows. </p>
<dd><p class="Body"><a name="90951"> </a>However, you can use the target server to create a dedicated console for virtual I/O. The option buttons in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Console and Redirection </font></b>property list (<a href="c-tools2.html#90958">Figure&nbsp;5-8</a>) direct virtual I/O to various locations: <div class="frame">
<h4 class="EntityTitle"><a name="90958"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 5-8:&nbsp;&nbsp;Virtual Console Properties</font></a></h4>

<dl class="margin">

<div class="Anchor"><a name="90963"> </a><img class="figure" border="0" src="images/c-tools9.gif">
</div>



</dl>

</div>
 </p>
</dl>

<dl class="margin">

<dd><div class="Item"><a name="90964"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Redirect Target IO </font></b></div>
<dl class="margin">

<dd><div class="Indent"><a name="90965"> </a>Redirect the target global <b class="symbol_lc">stdin</b>, <b class="symbol_lc">stdout</b>, and <b class="symbol_lc">stderr</b> to the target server. If the console is not created, WTX events are sent to all WTX tools when characters come from the target. </div>
<br>
</dl>

<dd><div class="Item"><a name="90966"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Create Console Window </font></b></div>
<dl class="margin">

<dd><div class="Indent"><a name="90967"> </a>Create a virtual console window on the target server host for target I/O. The <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Log Console</font></b> window (see <a href="c-tools3.html#89462"><i class="title">5.3&nbsp;Target Server Icon and Log Console Window</i></a>) is not used for this purpose.</div>
<br>
</dl>

<dd><div class="Item"><a name="90971"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Redirect Target Shell</font></b> </div>
<dl class="margin">

<dd><div class="Indent"><a name="90972"> </a>Start a console window into which the target shell's standard input, output, and error will be redirected. </div>
<br>
</dl>

</dl>

</dl>

<dl class="margin">
<dd>
<p class="table" callout>
<table border="0" cellpadding="0" cellspacing="0">
<tr valign="top">
<td valign="top" width="40">
<br>
<img border="0" alt="*" src="icons/note.gif">
</td>

<td>
<hr><div class="CalloutCell"><a name="90981"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE:  </font></b></a>See the <b class="command">tgtsvr</b> reference entry in <a href="x-toolman.html#83918"><i class="title">C.&nbsp;Tornado Tools Reference</i></a> for detailed information about these options and for other I/O options available with command-line usage.</div>
</td>


</tr>
<tr valign="top">
<td></td>

<td><hr></td>


</tr>

<tr valign="middle">
<td colspan="20">

</td>
</tr>
</table>
</p callout>



</dl>
<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="91004">Logging</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="91005"> </a>The <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Logging</font></b> property list (<a href="c-tools2.html#91012">Figure&nbsp;5-9</a>) allows you to log WDB and WTX requests. <div class="frame">
<h4 class="EntityTitle"><a name="91012"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 5-9:&nbsp;&nbsp;Logging Configuration Properties</font></a></h4>

<dl class="margin">

<div class="Anchor"><a name="91017"> </a><img class="figure" border="0" src="images/c-tools14.gif">
</div>



</dl>

</div>
</p>
</dl>

<dl class="margin">

<dd><div class="Item"><a name="91075"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Backend Log File</font></b></div>
<dl class="margin">

<dd><div class="Indent"><a name="91076"> </a>Log every WDB request sent to the target agent in this file. Back ends that are not based on WDB ignore this option. As with the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Verbose</font></b> toggle, a dedicated window appears to display the log.</div>
<br>
</dl>

<dd><div class="Item"><a name="91078"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Max Size</font></b></div>
<dl class="margin">

<dd><div class="Indent"><a name="91079"> </a>The maximum size of the back-end log file, in bytes. If defined, the file is limited to the specified size and written to as a circular file. That is, when the maximum size is reached, the file is rewritten from the beginning. If the file initially exists, it is deleted. This means that if the target server restarts (for example, due to a reboot), the log file will be reset. </div>
<br>
</dl>

<dd><div class="Item"><a name="91080"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">WTX Log file</font></b></div>
<dl class="margin">

<dd><div class="Indent"><a name="91081"> </a>Log every WTX request sent to the target server in the specified file. If the file exists, log messages will be appended (unless a maximum file size is set in <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">WTX Log file max size</font></b>, in which case it is overwritten).</div>
<br>
</dl>

<dd><div class="Item"><a name="91082"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Max Size</font></b></div>
<dl class="margin">

<dd><div class="Indent"><a name="91083"> </a>The maximum size of the WTX log file, in bytes. If defined, the file is limited to the specified size and written to as a circular file. That is, when the maximum size is reached, the file is rewritten from the beginning. If the file initially exists, it is deleted. This means that if the target server restarts (for example, due to a reboot), the log file will be reset. </div>
<br>
</dl>

<dd><div class="Item"><a name="91084"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Filter</font></b></div>
<dl class="margin">

<dd><div class="Indent"><a name="91085"> </a>Use this field to limit the amount of information written to a WTX log file. Enter a regular expression designed to filter out specific WTX requests. Default logging behavior may otherwise create a very large file, as all requests are logged.</div>
<br>
</dl>

</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="84335">Miscellaneous</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="84339"> </a>The <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Miscellaneous</font></b> property list (<a href="c-tools2.html#84348">Figure&nbsp;5-10</a>) provides for Tornado 1.0.1 tools compatibility, and for use of options that are not available through the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Configure Target Servers</font></b> dialog box. <div class="frame">
<h4 class="EntityTitle"><a name="84348"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 5-10:&nbsp;&nbsp;Miscellaneous Configuration Properties</font></a></h4>

<dl class="margin">

<div class="Anchor"><a name="84345"> </a><img class="figure" border="0" src="images/c-tools8.gif">
</div>



</dl>

</div>
</p>
</dl>

<dl class="margin">

<dd><div class="Item"><a name="91035"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Use portmapper</font></b></div>
<dl class="margin">

<dd><div class="Indent"><a name="91036"> </a>To register a target server with the RPC portmapper, turn on this checkbox. While the portmapper is not needed for Tornado 2.0, this option is included for development environments in which both Tornado 2.0 and Tornado 1.0.1 are in use. When both releases are in use, the portmapper must be used on:</div>
<br>
</dl>

<dl class="margin">

<p class="listspace">
<ul class="Bullet2" type="disc"><li><a name="91037"> </a>Any host running a Tornado 2.0 registry that will be accessed by any host running Tornado 1.0.1.</li></ul>
</p>
<p class="listspace">
<ul class="Bullet2" type="disc"><li><a name="91038"> </a>Any host running a Tornado 2.0 target server that will be accessed by any host running Tornado 1.0.1.</li></ul>
</p>
</dl>

<dl class="margin">

<dd><div class="Indent"><a name="91039"> </a>To use the portmapper when either a Tornado registry or target server is started from the command line, the <b class="command">-use_portmapper</b> option must be included. See the registry(<b class="command">wtxregd</b>) and target server(<b class="command">tgtsvr</b>) reference documentation in <i class="title">Tornado User's Guide: Tornado Tools Reference</i> for more information. </div>
<br>
</dl>

<dd><div class="Item"><a name="91108"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Other Options</font></b></div>
<dl class="margin">

<dd><div class="Indent"><a name="91110"> </a>Use this field to enter any options that are not otherwise available through the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Configure Target Servers </font></b>dialog box.</div>
<br>
</dl>

</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H3"><i><a name="86159">5.2.3  &nbsp;&nbsp;Using the Command Line</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="90015"> </a>In general, you will probably do most of your work from the Tornado IDE. In this case, you do not need to worry about environment variables: Tornado manages its internal environment automatically. However, if you also want to run some portions of Tornado from the command line (such as the compilation tools, or the shell), you must make sure that the appropriate variables are set in order for the tools to work properly. The file<b> </b><b class="file">torVars.bat</b> in <b>c:\tornado\host\x86-win32\bin</b> captures the requisite definitions, so that all you have to do is run <b>torVars.bat</b> to set the environment variables appropriately for your own Tornado installation. </p>
<dd><p class="Body"><a name="90014"> </a><b class="file"></b>You may want to start a server from the command line or from a batch file, so that your target is ready to use as soon as you enter the Tornado development environment. To do so, run <b class="file">c:\tornado\host\x86-win32\bin\tgtsvr.exe</b>. You must specify the network name of your target as an argument (see <a href="c-start3.html#84626"><i class="title">Establishing the VxWorks Target Name and IP Address</i></a>; and the <b class="command">tgtsvr</b> reference in <a href="x-toolman.html#83918"><i class="title">C.&nbsp;Tornado Tools Reference</i></a>). </p>
<dd><p class="Body"><a name="86181"> </a><b class="command"></b>There are a number of useful command-line options to <b class="command">tgtsvr</b> that control the behavior of your target server. These include the <b class="command">-V</b> (verbose) option for troubleshooting, the <b class="command">-B</b> option for alternative methods of communicating with the target, and several options for redirecting I/O. For detailed information on these and other command-line options, see the <b class="command">tgtsvr</b> reference entry in <a href="x-toolman.html#83918"><i class="title">C.&nbsp;Tornado Tools Reference</i></a>. </p>
</dl>

</dl>


<a name="foot"><hr></a>


<p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="GuideIX.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-tools.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-tools1.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-tools3.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p>

</body>

</html>
<!---
by WRS Documentation (), Wind River Systems, Inc.
    conversion tool:  Quadralay WebWorks Publisher 4.0.11
    template:         CSS Template, Jan 1998 - Jefro --->