[TeamTalk 208]: [744] trunk/moast-bth/moast/doc/refManual_tex: Import more documentation.

[tk@edam.speech.cs.cmu.edu]

An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/teamtalk-developers/attachments/20070914/3a323b3c/attachment.html
-------------- next part --------------
Modified: trunk/moast-bth/moast/doc/refManual_tex/modToMod/config.tex
===================================================================
--- trunk/moast-bth/moast/doc/refManual_tex/modToMod/config.tex	2007-09-13 17:42:11 UTC (rev 743)
+++ trunk/moast-bth/moast/doc/refManual_tex/modToMod/config.tex	2007-09-14 15:06:57 UTC (rev 744)
@@ -1,5 +1,5 @@
 \subsection{Configuration File}
-NML uses text files to hold configurations information, not a central server or database. This file may be stored on a central file server or may be copied and distributed redundantly. The configuration file contains two sections; one for a description of NML buffers and the other for descriptions of NML processes. In the MOAST framework, the configuration file is called \texttt{MOAST\_TOP/devel/etc/moast.cfg}. Automatic tools are used on this file in order to generate the actual configuration file used by the system. This file is \texttt{MOAST\_TOP/devel/etc/moast.nml}.
+NML uses text files to hold configurations information, not a central server or database. This file may be stored on a central file server or may be copied and distributed redundantly. The configuration file contains two sections; one for a description of NML buffers and the other for descriptions of NML processes. In the MOAST framework, the configuration file is called \texttt{MOAST\_TOP/devel/etc/moast.cfg}. Automatic tools are used on this file in order to generate the actual configuration file used by the system. This file is \texttt{MOAST\_TOP/devel/etc/moast.nml}. More detailed information on the configuration file may be found at \href{http://www.isd.mel.nist.gov/projects/rcslib/NMLcfg.html}.
 
 \fcolorbox{Dark}{Light}{
 \begin{minipage}{6in}
@@ -28,7 +28,7 @@
 \item {\bf bufname} - the name of the buffer to connect to. This must match one of the buffer lines.
 \item {\bf name} - the name of the process connecting to the buffer. If this is set to ``default'', then this process line will be used by any process connecting to this buffer not specifically listed earlier.
 \item {\bf master} - set to 0 if this process is not to create the NML buffer, 1 if it is. Under the MOAST framework, the server always creates the buffer, so ``master'' and ``server'' should have the same value.
-\item {\bf server} - set to 0 if this process is not to be an NML server, and 1 if it is.
+\item {\bf server} - should be either 0, 1, 2, or 3. A 1 indicates that this process is responsible for running a server for the buffer, a 2 indicates that the {\it nml\_start} function should spawn a server for the buffer, and a 0 is for processes that will neither spawn nor run a server for the buffer. 
 \item {\bf proctype} - this may be local, remote, or auto. Local means that this process resides on the same host as the buffer (for shared memory or local memory access), the same file system as the buffer (for file memory access), or the same backplane as the buffer (for global memory access). Remote means not local. Java applications should use remote. Auto will revert to local if the host on the buffer line matches the process hostname and remote otherwise.
 \end{itemize}
 

Modified: trunk/moast-bth/moast/doc/refManual_tex/tools.tex
===================================================================
--- trunk/moast-bth/moast/doc/refManual_tex/tools.tex	2007-09-13 17:42:11 UTC (rev 743)
+++ trunk/moast-bth/moast/doc/refManual_tex/tools.tex	2007-09-14 15:06:57 UTC (rev 744)
@@ -1,4 +1,5 @@
 \input{tools/libraries}
 \input{tools/tools}
 \input{tools/joystick}
+\input{tools/linkMon}