📄 netware.html.en
字号:
</code></p></div> <p>or</p> <div class="example"><p><code> apache2 shutdown </code></p></div> <p>If apache is running in a protected address space specify the address space in the unload statement:</p> <div class="example"><p><code> unload address space = apache2 apache2 </code></p></div> <p>When working with Apache it is important to know how it will find the configuration files. You can specify a configuration file on the command line in two ways:</p> <ul> <li><code>-f</code> specifies a path to a particular configuration file</li> </ul> <div class="example"><p><code> apache2 -f "vol:/my server/conf/my.conf" </code></p></div> <div class="example"><p><code> apache -f test/test.conf </code></p></div> <p>In these cases, the proper <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> should be set in the configuration file.</p> <p>If you don't specify a configuration file name with <code>-f</code>, Apache will use the file name compiled into the server, usually <code>conf/httpd.conf</code>. Invoking Apache with the <code>-V</code> switch will display this value labeled as <code>SERVER_CONFIG_FILE</code>. Apache will then determine its <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> by trying the following, in this order:</p> <ul> <li>A <code>ServerRoot</code> directive via a <code>-C</code> switch.</li> <li>The <code>-d</code> switch on the command line.</li> <li>Current working directory</li> <li>The server root compiled into the server.</li> </ul> <p>The server root compiled into the server is usually <code>sys:/apache2</code>. invoking apache with the <code>-V</code> switch will display this value labeled as <code>HTTPD_ROOT</code>.</p> <p>Apache 2.0 for NetWare includes a set of command line directives that can be used to modify or display information about the running instance of the web server. These directives are only available while Apache is running. Each of these directives must be preceded by the keyword <code>APACHE2</code>.</p> <dl> <dt>RESTART</dt> <dd>Instructs Apache to terminate all running worker threads as they become idle, reread the configuration file and restart each worker thread based on the new configuration.</dd> <dt>VERSION</dt> <dd>Displays version information about the currently running instance of Apache.</dd> <dt>MODULES</dt> <dd>Displays a list of loaded modules both built-in and external.</dd> <dt>DIRECTIVES</dt> <dd>Displays a list of all available directives.</dd> <dt>SETTINGS</dt> <dd>Enables or disables the thread status display on the console. When enabled, the state of each running threads is displayed on the Apache console screen.</dd> <dt>SHUTDOWN</dt> <dd>Terminates the running instance of the Apache web server.</dd> <dt>HELP</dt> <dd>Describes each of the runtime directives.</dd> </dl> <p>By default these directives are issued against the instance of Apache running in the OS address space. To issue a directive against a specific instance running in a protected address space, include the -p parameter along with the name of the address space. For more information type "apache2 Help" on the command line.</p> </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="use" id="use">Configuring Apache for NetWare</a></h2> <p>Apache is configured by reading configuration files usually stored in the <code>conf</code> directory. These are the same as files used to configure the Unix version, but there are a few different directives for Apache on NetWare. See the <a href="../">Apache documentation</a> for all the available directives.</p> <p>The main differences in Apache for NetWare are:</p> <ul> <li> <p>Because Apache for NetWare is multithreaded, it does not use a separate process for each request, as Apache does on some Unix implementations. Instead there are only threads running: a parent thread, and multiple child or worker threads which handle the requests.</p> <p>Therefore the "process"-management directives are different:</p> <p><code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code> - Like the Unix directive, this controls how many requests a worker thread will serve before exiting. The recommended default, <code>MaxRequestsPerChild 0</code>, causes the thread to continue servicing request indefinitely. It is recommended on NetWare, unless there is some specific reason, that this directive always remain set to <code>0</code>.</p> <p><code class="directive"><a href="../mod/mpm_common.html#startthreads">StartThreads</a></code> - This directive tells the server how many threads it should start initially. The recommended default is <code>StartThreads 50</code>.</p> <p><code class="directive"><a href="../mod/mpm_common.html#minsparethreads">MinSpareThreads</a></code> - This directive instructs the server to spawn additional worker threads if the number of idle threads ever falls below this value. The recommended default is <code>MinSpareThreads 10</code>.</p> <p><code class="directive"><a href="../mod/mpm_common.html#maxsparethreads">MaxSpareThreads</a></code> - This directive instructs the server to begin terminating worker threads if the number of idle threads ever exceeds this value. The recommended default is <code>MaxSpareThreads 100</code>.</p> <p><code class="directive"><a href="../mod/mpm_netware.html#maxthreads">MaxThreads</a></code> - This directive limits the total number of work threads to a maximum value. The recommended default is <code>ThreadsPerChild 250</code>.</p> <p><code class="directive"><a href="../mod/mpm_common.html#threadstacksize">ThreadStackSize</a></code> - This directive tells the server what size of stack to use for the individual worker thread. The recommended default is <code>ThreadStackSize 65536</code>.</p> </li> <li> <p>The directives that accept filenames as arguments must use NetWare filenames instead of Unix names. However, because Apache uses Unix-style names internally, forward slashes must be used rather than backslashes. It is recommended that all rooted file paths begin with a volume name. If omitted, Apache will assume the <code>SYS:</code> volume which may not be correct.</p> </li> <li> <p>Apache for NetWare has the ability to load modules at runtime, without recompiling the server. If Apache is compiled normally, it will install a number of optional modules in the <code>\Apache2\modules</code> directory. To activate these, or other modules, the <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code> directive must be used. For example, to active the status module, use the following:</p> <div class="example"><p><code> LoadModule status_module modules/status.nlm </code></p></div> <p>Information on <a href="../mod/mod_so.html#creating">creating loadable modules</a> is also available.</p> </li> </ul> <h3><a name="use-add" id="use-add">Additional NetWare specific directives:</a></h3> <ul> <li><code class="directive"><a href="../mod/core.html#cgimapextension">CGIMapExtension</a></code> - This directive maps a CGI file extension to a script interpreter.</li> </ul> <ul> <li><code class="directive"><a href="../mod/mod_nw_ssl.html#securelisten">SecureListen</a></code> - Enables SSL encryption for a specified port.</li> </ul> <ul> <li><code class="directive"><a href="../mod/mod_nw_ssl.html#nwssltrustedcerts">NWSSLTrustedCerts</a></code> - Adds trusted certificates that are used to create secure connections to proxied servers.</li> </ul> <ul> <li><code class="directive"><a href="../mod/mod_nw_ssl.html#nwsslupgradeable">NWSSLUpgradeable</a></code> - Allow a connection created on the specified address/port to be upgraded to an SSL connection.</li> </ul> </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="comp" id="comp">Compiling Apache for NetWare</a></h2> <p>Compiling Apache requires MetroWerks CodeWarrior 6.x or higher. Once Apache has been built, it can be installed to the root of any NetWare volume. The default is the <code>sys:/Apache2</code> directory.</p> <p>Before running the server you must fill out the <code>conf</code> directory. Copy the file <code>HTTPD-STD.CONF</code> from the distribution <code>conf</code> directory and rename it to <code>HTTPD.CONF</code>. Edit the <code>HTTPD.CONF</code> file searching for all <code>@@Value@@</code> markers and replacing them with the appropriate setting. Copy over the <code>conf/magic</code> and <code>conf/mime.types</code> files as well. Alternatively, a complete distribution can be built by including the keyword <code>install</code> when invoking the makefiles.</p>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -