Starting and Stopping AppWeb (Manually)

After installation, AppWeb is normally started automatically as a system service or system daemon. You can change this behavior and only start AppWeb manually if you wish.

This page gives information about starting and stopping AppWeb manually. Before you can run AppWeb manually, you must first stop it running as a system service. See Running as a service for how to stop AppWeb running as a system service.

AppWeb Programs

On Windows there are two AppWeb programs to choose from:
  • appWeb
  • winAppWeb
On Windows, the winAppWeb program is the default AppWeb application. It is a windows application that can be run from the Start menu or as a system service. It does not require a DOS console in which to execute.

On Unix / Linux, the appWeb program is the only AppWeb program. It can be run either from a console terminal window or it can be run as a system daemon. The appWeb program is also available on Windows and is ideal for debugging purposes when trace to the console can assist in fault finding.

AppWeb Command Line

Both the appWeb and winAppWeb programs may be invoked from the command line. The command syntax is:

appWeb [options]
or
winAppWeb [options]

AppWeb Command Options

Option
Description
-c
Display the parsed appWeb configuration to stdout. Very useful for debugging the configuration file.
-d
Run appWeb as a daemon in the background.
-D
Set DEBUG mode on. This will disable all timeouts and is useful for single-step debugging.
-f configFile
Specifies an alternative configuration file instead of appWeb.conf.
-k
Kill a currently running appWeb. Not yet implemented.
-l logSpec
Specify a file to log messages. This will override the ErrorLog directive in the configuration file. The syntax is: -l logName[,moduleName][:logLevel][.maxSize]. When the maximum size is exceeded, the log file will be rotated to logName.old and a new log file will be started.
-m
Dump memory statistics when exiting. Only active if using the fast malloc allocator if the  MPR_FEATURE_MALLOC and MPR_FEATURE_MALLOC_STATS have been selected when building the source. The default binary build does not enable these.
-p numPoolThreads
Specify the number of threads to allocate for the appWeb thread pool. This overrides the ThreadLimit configuration file directive.
-r serverRootDir
Specify the starting directory for the root of the server. This directory contains AppWeb configuration file.
-T
Display timestamps of key events in the log file. This is activated only if the source is built with MPR_FEATURE_DEBUG.
-V
Display the appWeb version number

WinAppWeb Command Options

The winAppWeb program also supports the following options:

-d
Run winAppWeb as a Windows service (daemon). Do not use this switch when invoking winAppWeb from the command line as it will attempt to connect with the Service Control manager and will hang for 10 seconds before continuing.
-i "service command line"
Install winAppWeb as a windows service. The argument to the -i option is a winAppWeb set of options to use when the Windows service control manager starts winAppWeb. The argument to -i is normall "-d" to instruct winAppWeb to run as a windows service.
-g
Instruct winAppWeb to go (start).
-s
Stop winAppWeb.
-u
Uninstall winAppWeb as a system service.


© Mbedthis Software LLC, 2003-2204. All rights reserved. Mbedthis is a trademark of Mbedthis Software LLC.