Changeset 8403

Show
Ignore:
Timestamp:
10/31/08 15:58:20 (5 years ago)
Author:
mcarrick
Message:

added nodebooter clean up section

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • documentation/ossie/user-guide-0.7.0/RunningWaveforms.tex

    r8281 r8403  
    2828because nodeBooter uses paths that are defined relatively to the directory in 
    2929which it is run. 
     30 
     31\subsection{Nodebooter Clean-Up} 
     32If a waveform crashes or is uninstalled incorrectly, Nodebooter will not be 
     33able to shut down all of the processes that it starts. This is currently  
     34being addressed by the development team, however in the interim the processes 
     35must be stopped by hand. To find which processes were not stopped, enter the  
     36following command: 
     37\begin{lstlisting}[] 
     38 $ ps -e 
     39\end{lstlisting} 
     40 
     41This will list all of the currently running processes. Processes with the names 
     42of components or devices that are in the waveform need to be shutdown. To stop 
     43a process, enter the following command: 
     44\begin{lstlisting}[] 
     45 $ killall USRP GPP <MORE-DEVICES> TxDemo Decimator <MORE-COMPONENTS> 
     46\end{lstlisting} 
     47 
     48If the USRP node (default\_GPP\_USRP\_sound\_node) cannot be started, this is 
     49typically resolved by killing the USRP, soundCardPlayback and soundCardCapture 
     50devices. 
     51 
     52To make this process faster, create a script to kill all of the processes created 
     53by a certain waveform. For example, create a text file called {\tt killOSSIEDemo}. 
     54\begin{lstlisting}[] 
     55 $ cd ~ 
     56 $ vim killOSSIEDemo 
     57\end{lstlisting} 
     58 
     59In this text file, press {\tt i} to insert text and enter the following on a single  
     60line: 
     61\begin{lstlisting}[] 
     62 killall GPP TxDemo ChannelDemo RxDemo 
     63\end{lstlisting} 
     64 
     65Press {\tt <ESC>}, {\tt :wq}, and then {\tt <ENTER>} to save the file and exit. Now  
     66change the permissions so the script can be executed. 
     67 
     68\begin{lstlisting}[] 
     69 $ chmod +x killOSSIEDemo 
     70\end{lstlisting} 
     71 
     72Now the script has been created and can be run by entering the command: 
     73\begin{lstlisting}[] 
     74 $ ./killOSSIEDemo 
     75\end{lstlisting} 
     76 
     77If not all processes within the script are running a warning will be printed stating  
     78that the process has not been killed, which is fine. 
     79 
    3080 
    3181\subsection{Loading a Waveform}