Changes between Version 27 and Version 28 of startstop


Ignore:
Timestamp:
11/15/11 16:38:51 (10 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • startstop

    v27 v28  
    5555 * Note that the <module name> must be unique for this to work as an argument. The command line version can only accept the pid (Process Id) as an argument. 
    5656 
    57 === StartstopConsole === 
     57=== !StartstopConsole === 
    5858Creates a command prompt window with access to startstop_service (Windows only). 
     59 
     60 * The !StartstopConsole connects to a running instance of Windows Startstop via named pipes and creates a Windows command prompt window. It's useful when running Startstop Service, and you need to apply command line tools like "restart", "reconfigure", "status", "pidpau" or "pau". 
     61 
     62 * Configuration Hint: In order to get this to work on XP you need to disable the "XP Welcome screen" and disable "Fast user switching" 
    5963 
    6064=== status === 
     
    9296}}} 
    9397 
    94 '''Windows, Windows Service version:''' 
     98== Windows, Windows Service version == 
    9599 
    96100 * Windows startstop and Windows startstop service read a configuration file named 'startstop_nt.d' 
    97101 * 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". 
    98  * 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. 
    99  
    100 === Instructions for Running Startstop in Background === 
     102 * 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 above: !StartstopConsole). You'll be able to start and stop Earthworm with the Windows Services Control Panel. 
     103 
     104== Instructions for Running Startstop in Background == 
    101105To run startstop in background from the run/params directory with shells like csh, use a command like: 
    102106 
     
    111115Also, you should wait a few seconds after starting Earthworm before running "status", to let the Earthworm modules get going. 
    112116 
    113 === Startstop File Characteristics === 
     117== Startstop File Characteristics == 
    114118For a more secure operation Earthworm should be run by a user other than root; however, some modules need to have root permissions to set their priority. To set it up to do this you should: 
    115119 
     
    124128You should now be able to run earthworm without being root. 
    125129 
    126 ==== Earthworm NT Autostart ==== 
     130== Earthworm NT Autostart == 
    127131Following are steps needed to have earthworm (EW) start up automatically when a PC running Windows NT Workstation 4.0 boots up. 
    128132 
     
    244248 
    245249 
    246  
    247 ==== !StartstopConsole Overview (Windows Only) ==== 
    248 The !StartstopConsole connects to a running instance of Windows Startstop via named pipes and creates a Windows command prompt window. It's useful when running Startstop Service, and you need to apply command line tools like "restart", "reconfigure", "status", "pidpau" or "pau". 
    249  
    250 Configuration Hint In order to get this to work on XP you need to disable the "XP Welcome screen" and disable "Fast user switching"