Changes between Version 11 and Version 12 of Installation_and_Configuration


Ignore:
Timestamp:
11/16/11 13:07:11 (10 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Installation_and_Configuration

    v11 v12  
    253253* Carl Trig: [wiki:carlstatrig carlstatrig] and [wiki:carlsubtrig carlsubtrig] 
    254254 
    255 * HypoInverse: [wiki:eqproc eqproc], ... , [wiki:hypoinverse hypoinverse] 
     255* HypoInverse: [wiki:eqproc eqproc], ... 
    256256 
    257257* See [wiki:Earthworm Earthworm] for a comprehensive list of available modules.  
     
    273273== 11. DEBUGGING TOOLS AND HINTS == 
    274274 
    275 In the startstop configuration file ([wiki:startstop_nt startstop_nt].d), each module which is to be run has a "NewConsole" / "NoNewConsole" specification. This determines whether the module's standard output is written to its own command window or into the window used to start the system. For initial testing, it is recommended to set all these to "NoNewConsole". In routine operation, individual windows are convenient for checking on system status. During initial debugging, however, modules tend to exit due to gross configuration errors (typical are invalid "Module Id" and "Ring Name" values). Under Windows 2000 this causes the window of the deceased module to vanish, carrying with it the module's error messages. The "NoNewConsole" setting permits the user to analyze terminal error messages. 
     275In the startstop configuration file ([wiki:startstop_nt startstop_nt].d), each module which is to be run has a "!NewConsole" / "!NoNewConsole" specification. This determines whether the module's standard output is written to its own command window or into the window used to start the system. For initial testing, it is recommended to set all these to "!NoNewConsole". In routine operation, individual windows are convenient for checking on system status. During initial debugging, however, modules tend to exit due to gross configuration errors (typical are invalid "Module Id" and "Ring Name" values). Under Windows 2000 this causes the window of the deceased module to vanish, carrying with it the module's error messages. The "!NoNewConsole" setting permits the user to analyze terminal error messages. 
    276276 
    277277As mentioned above, Earthworm includes a logging scheme in which each module can produce a log file in the /run/log directory. When a module has identity information to create a log file, it will do so, creating a new log file at midnight. These log files are the primary method for analyzing system malfunctions after initial setup. Note that under Windows 2000,a log file which is in use cannot be edited. One solution is to copy the current log file to a scratch file, and then look at that scratch file with an editor.