Changes between Version 22 and Version 23 of startstop


Ignore:
Timestamp:
11/14/11 13:33:30 (10 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • startstop

    v22 v23  
    1212Note that two copies of startstop pointing at the same startstop *d file are not allowed to run simultaneously. The second one started will fail and quit. (If you really want to do this for some reason, you'd need to make sure that you use all different rings in the second version, different ports for the modules, and a different startstop*d file, specified as a parameter when starting startstop.) 
    1313 
    14 If the user presses the "Enter" key while the startstop command window is Selected, or enters the command "status", startstop will print a status table showing various statistics for each module, including whether it is dead or alive. If a module is dead because it could not be started (for example, the executable's name were mistyped so the executable could not be found), it will be reported as NoExec. 
     14If the user presses the "Enter" key while the startstop command window is Selected, or enters the command "status", startstop will print a status table showing various statistics for each module, including whether it is dead or alive. If a module is dead because it could not be started (for example, the executable's name were mistyped so the executable could not be found), it will be reported as !NoExec. 
    1515 
    1616Startstop will also react to 'restart' messages from statmgr. This is part of a scheme wich works as follows: A module may have the token "restartMe" it its .desc file (the file given to statmgr, which tells it how to process exception conditions from that module). If its heartbeat ceases, statmgr will send a restart request to startstop. Startstop will then kill the offending module, and restart it with the same arguments as it did at startup time. There are some system specific features, listed below: 
     
    6262 
    6363 * Windows startstop and Windows startstop service read a configuration file named 'startstop_nt.d' 
    64  * If Windows starts up, and, for example, the binary executables for certain modules are missing or are misnamed, startstop will start up anyway. These processes will be shown with a nonexistent negative process ID, and "NoExec" as their status. If this process is restarted once the problem that caused the error has been fixed, the process ID will return to a normal ID, and the status will change to "Alive". 
     64 * If Windows starts up, and, for example, the binary executables for certain modules are missing or are misnamed, startstop will start up anyway. These processes will be shown with a nonexistent negative process ID, and "!NoExec" as their status. If this process is restarted once the problem that caused the error has been fixed, the process ID will return to a normal ID, and the status will change to "Alive". 
    6565 * Startstop can be set to start automatically when Windows boots up (see below: 'Earthworm NT Autostart'), but probably better than doing that is to set startstop as a Windows service (see below: Earthworm Windows Service). Note if you set Startstop as a Windows service you'll need to use other command line utilities like 'status' and 'restart' to monitor and control earthworm modules since there's no interface to the Startstop service. You can run !StartstopConsole in order to be able to connect to the session running earthworm, if you're not logged in as administrator (see below: !StartstopConsole Overview). You'll be able to start and stop Earthworm with the Windows Services Control Panel. 
    6666 
     
    135135 
    136136c. HKEY_LOCAL_MACHINE window should come to the foreground. Double click on the following: 
    137 Software->Microsoft->WindowsNT->CurrentVersion->WinLogon 
     137Software->Microsoft->WindowsNT->!CurrentVersion->!WinLogon 
    138138 
    139139d. Now we need to create and/or set some values in the registry in the right hand section of the window. 
    140 i. AutoAdminLogon 
    141 If the AutoAdminLogon exits: 
    142 Double click on the AutoAdminLogon field. Enter 1 in the pop up window. 
    143  
    144 If the AutoAdminLogon does not exit: From the EDIT pull down menu, Select AddValue. In the pop up window, enter "AutoAdminLogon" in the ValueName box.  Choose 'REG_SZ' for the data type.  Click OK. Enter 1 in the next pop up window; then click OK. 
    145  
    146 ii. DefaultUserName 
     140i. !AutoAdminLogon 
     141If the !AutoAdminLogon exits: 
     142Double click on the !AutoAdminLogon field. Enter 1 in the pop up window. 
     143 
     144If the !AutoAdminLogon does not exit: From the EDIT pull down menu, Select !AddValue. In the pop up window, enter "!AutoAdminLogon" in the ValueName box.  Choose 'REG_SZ' for the data type.  Click OK. Enter 1 in the next pop up window; then click OK. 
     145 
     146ii. !DefaultUserName 
    147147Click on Edit->Add Value. A dialog box should come up. Fill in: 
    148 Value Name:    DefaultUserName   click OK, another window comes up. Fill in: 
     148Value Name:    !DefaultUserName   click OK, another window comes up. Fill in: 
    149149String: earthworm 
    150150Click OK. 
    151151 
    152 iii. DefaultPassword 
     152iii. !DefaultPassword 
    153153Follow the step above to add another value: 
    154154 
    155 Value Name:    DefaultPassword 
     155Value Name:    !DefaultPassword 
    156156String:        earthworm 
    157157 
    158158When all is said and done, the following values whould be listed inthe right hand window: 
    159159 
    160 DefaultUserName     earthworm 
    161 DefaultPassword     earthworm 
    162 AutoAdminLogon      1 
     160!DefaultUserName     earthworm 
     161!DefaultPassword     earthworm 
     162!AutoAdminLogon      1 
    163163 
    164164e. Click on Registry->Exit