1
<?xml version="1.0" encoding="ISO-8859-1"?>
2
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
4
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
5
This file is generated from xml source: DO NOT EDIT
6
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
8
<title>Using Apache With Novell NetWare - Apache HTTP Server</title>
9
<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
10
<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
11
<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
12
<link href="../images/favicon.ico" rel="shortcut icon" /></head>
13
<body id="manual-page"><div id="page-header">
14
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
15
<p class="apache">Apache HTTP Server Version 2.2</p>
16
<img alt="" src="../images/feather.gif" /></div>
17
<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
19
<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.2</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Using Apache With Novell NetWare</h1>
21
<p><span>Available Languages: </span><a href="../en/platform/netware.html" title="English"> en </a> |
22
<a href="../ko/platform/netware.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
26
<p>This document explains how to install, configure and run
27
Apache 2.0 under Novell NetWare 6.0 and above. If you find any bugs,
28
or wish to contribute in other ways, please use our
29
<a href="http://httpd.apache.org/bug_report.html">bug reporting
32
<p>The bug reporting page and dev-httpd mailing list are <em>not</em>
33
provided to answer questions about configuration or running Apache.
34
Before you submit a bug report or request, first consult this document, the
35
<a href="../faq/">Frequently Asked Questions</a> page and the other
36
relevant documentation topics. If you still have a question or problem,
37
post it to the <a href="news://developer-forums.novell.com/novell.devsup.webserver">
38
novell.devsup.webserver</a> newsgroup, where many Apache users are more than
39
willing to answer new and obscure questions about using Apache on NetWare.</p>
41
<p>Most of this document assumes that you are installing Apache
42
from a binary distribution. If you want to compile Apache
43
yourself (possibly to help with development, or to track down
44
bugs), see the section on <a href="#comp">Compiling Apache for
45
NetWare</a> below.</p>
48
<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">Requirements</a></li>
49
<li><img alt="" src="../images/down.gif" /> <a href="#down">Downloading Apache for NetWare</a></li>
50
<li><img alt="" src="../images/down.gif" /> <a href="#inst">Installing Apache for NetWare</a></li>
51
<li><img alt="" src="../images/down.gif" /> <a href="#run">Running Apache for NetWare</a></li>
52
<li><img alt="" src="../images/down.gif" /> <a href="#use">Configuring Apache for NetWare</a></li>
53
<li><img alt="" src="../images/down.gif" /> <a href="#comp">Compiling Apache for NetWare</a></li>
55
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
57
<h2><a name="req" id="req">Requirements</a></h2>
61
<p>Apache 2.0 is designed to run on NetWare 6.0 service pack 3
62
and above. If you are running a service pack less
63
than SP3, you must install the latest
64
<a href="http://developer.novell.com/ndk/libc.htm">NetWare Libraries
67
<p>NetWare service packs are available <a href="http://support.novell.com/misc/patlst.htm#nw">here</a>.</p>
69
<p>Apache 2.0 for NetWare can also be run in a NetWare 5.1 environment
70
as long as the latest service pack or the latest version
71
of the <a href="http://developer.novell.com/ndk/libc.htm">NetWare Libraries
72
for C (LibC)</a> has been installed . <strong>WARNING:</strong> Apache 2.0
73
for NetWare has not been targeted for or tested in this environment.</p>
75
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
77
<h2><a name="down" id="down">Downloading Apache for NetWare</a></h2>
81
<p>Information on the latest version of Apache can be found on
82
the Apache web server at <a href="http://www.apache.org/">http://www.apache.org/</a>. This
83
will list the current release, any more recent alpha or
84
beta-test releases, together with details of mirror web and
85
anonymous ftp sites. Binary builds of the latest releases of
86
Apache 2.0 for NetWare can be downloaded from
87
<a href="http://www.apache.org/dist/httpd/binaries/netware">here</a>.</p>
89
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
91
<h2><a name="inst" id="inst">Installing Apache for NetWare</a></h2>
95
<p>There is no Apache install program for NetWare currently. If you
96
are building Apache 2.0 for NetWare from source, you will need to
97
copy the files over to the server manually.</p>
99
<p>Follow these steps to install Apache on NetWare from the
100
binary download (assuming you will install to
101
<code>sys:/apache2</code>):</p>
104
<li>Unzip the binary download file to the root of the <code>SYS:</code>
105
volume (may be installed to any volume)</li>
107
<li>Edit the <code>httpd.conf</code> file setting <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> and <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> along with any file path values
108
to reflect your correct server settings</li>
110
<li>Add <code>SYS:/APACHE2</code> to the search path, for example:
111
<div class="example"><p><code>SEARCH ADD SYS:\APACHE2</code></p></div>
116
<p>Follow these steps to install Apache on NetWare manually
117
from your own build source (assuming you will install to
118
<code>sys:/apache2</code>):</p>
121
<li>Create a directory called <code>Apache2</code> on a
124
<li>Copy <code>APACHE2.NLM</code>, <code>APRLIB.NLM</code>
125
to <code>SYS:/APACHE2</code></li>
127
<li>Create a directory under <code>SYS:/APACHE2</code>
128
called <code>BIN</code></li>
130
<li>Copy <code>HTDIGEST.NLM</code>, <code>HTPASSWD.NLM</code>,
131
<code>HTDBM.NLM</code>, <code>LOGRES.NLM</code>, <code>ROTLOGS.NLM</code>
132
to <code>SYS:/APACHE2/BIN</code></li>
134
<li>Create a directory under <code>SYS:/APACHE2</code>
135
called <code>CONF</code></li>
137
<li>Copy the <code>HTTPD-STD.CONF</code> file to the
138
<code>SYS:/APACHE2/CONF</code> directory and rename to
139
<code>HTTPD.CONF</code></li>
141
<li>Copy the <code>MIME.TYPES</code>, <code>CHARSET.CONV</code> and
142
<code>MAGIC</code> files to <code>SYS:/APACHE2/CONF</code> directory</li>
144
<li>Copy all files and subdirectories in <code>\HTTPD-2.0\DOCS\ICONS</code>
145
to <code>SYS:/APACHE2/ICONS</code></li>
147
<li>Copy all files and subdirectories in <code>\HTTPD-2.0\DOCS\MANUAL</code>
148
to <code>SYS:/APACHE2/MANUAL</code></li>
150
<li>Copy all files and subdirectories in <code>\HTTPD-2.0\DOCS\ERROR</code>
151
to <code>SYS:/APACHE2/ERROR</code></li>
153
<li>Copy all files and subdirectories in <code>\HTTPD-2.0\DOCS\DOCROOT</code>
154
to <code>SYS:/APACHE2/HTDOCS</code></li>
156
<li>Create the directory <code>SYS:/APACHE2/LOGS</code>
159
<li>Create the directory <code>SYS:/APACHE2/CGI-BIN</code>
162
<li>Create the directory <code>SYS:/APACHE2/MODULES</code>
163
and copy all nlm modules into the <code>modules</code> directory</li>
165
<li>Edit the <code>HTTPD.CONF</code> file searching for all
166
<code>@@Value@@</code> markers and replacing them with the
167
appropriate setting</li>
169
<li>Add <code>SYS:/APACHE2</code> to the search path, for example:
170
<div class="example"><p><code>SEARCH ADD SYS:\APACHE2</code></p></div>
174
<p>Apache may be installed to other volumes besides the default <code>SYS</code> volume.</p>
176
<p>During the build process, adding the keyword "install" to the makefile command line
177
will automatically produce a complete distribution package under the subdirectory
178
<code>DIST</code>. Install Apache by simply copying the distribution that was produced
179
by the makfiles to the root of a NetWare volume (see: <a href="#comp">Compiling Apache for
180
NetWare</a> below).</p>
182
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
183
<div class="section">
184
<h2><a name="run" id="run">Running Apache for NetWare</a></h2>
188
<p>To start Apache just type <code>apache</code> at the
189
console. This will load apache in the OS address space. If you
190
prefer to load Apache in a protected address space you may
191
specify the address space with the load statement as follows:</p>
193
<div class="example"><p><code>
194
load address space = apache2 apache2
197
<p>This will load Apache into an address space called apache2.
198
Running multiple instances of Apache concurrently on NetWare is
199
possible by loading each instance into its own protected
202
<p>After starting Apache, it will be listening to port 80
203
(unless you changed the <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>
204
directive in the configuration files).
205
To connect to the server and access the default page,
206
launch a browser and enter the server's name or address. This
207
should respond with a welcome page, and a link to the Apache
208
manual. If nothing happens or you get an error, look in the
209
<code>error_log</code> file in the <code>logs</code>
212
<p>Once your basic installation is working, you should
213
configure it properly by editing the files in the
214
<code>conf</code> directory.</p>
216
<p>To unload Apache running in the OS address space just type
217
the following at the console:</p>
219
<div class="example"><p><code>
225
<div class="example"><p><code>
229
<p>If apache is running in a protected address space specify the
230
address space in the unload statement:</p>
232
<div class="example"><p><code>
233
unload address space = apache2 apache2
236
<p>When working with Apache it is important to know how it will
237
find the configuration files. You can specify a configuration
238
file on the command line in two ways:</p>
241
<li><code>-f</code> specifies a path to a particular
242
configuration file</li>
245
<div class="example"><p><code>
246
apache2 -f "vol:/my server/conf/my.conf"
249
<div class="example"><p><code>
250
apache -f test/test.conf
253
<p>In these cases, the proper <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>
254
should be set in the configuration file.</p>
256
<p>If you don't specify a configuration file name with <code>-f</code>,
257
Apache will use the file name compiled into the server, usually
258
<code>conf/httpd.conf</code>. Invoking Apache with the <code>-V</code>
259
switch will display this value labeled as <code>SERVER_CONFIG_FILE</code>.
260
Apache will then determine its <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>
261
by trying the following, in this order:</p>
264
<li>A <code>ServerRoot</code> directive via a
265
<code>-C</code> switch.</li>
267
<li>The <code>-d</code> switch on the command line.</li>
269
<li>Current working directory</li>
271
<li>The server root compiled into the server.</li>
274
<p>The server root compiled into the server is usually <code>sys:/apache2</code>.
275
invoking apache with the <code>-V</code> switch will display this value labeled as
276
<code>HTTPD_ROOT</code>.</p>
278
<p>Apache 2.0 for NetWare includes a set of command line directives that can
279
be used to modify or display information about the running instance of the
280
web server. These directives are only available while Apache is running. Each
281
of these directives must be preceded by the keyword <code>APACHE2</code>.</p>
285
<dd>Instructs Apache to terminate all running worker
286
threads as they become idle, reread the configuration file and restart each
287
worker thread based on the new configuration.</dd>
290
<dd>Displays version information about the currently
291
running instance of Apache.</dd>
294
<dd>Displays a list of loaded modules both built-in
298
<dd>Displays a list of all available directives.</dd>
301
<dd>Enables or disables the thread status display
302
on the console. When enabled, the state of each running threads is displayed
303
on the Apache console screen.</dd>
306
<dd>Terminates the running instance of the Apache
310
<dd>Describes each of the runtime directives.</dd>
313
<p>By default these directives are issued against the instance of Apache running
314
in the OS address space. To issue a directive against a specific instance running
315
in a protected address space, include the -p parameter along with the name of the
316
address space. For more information type "apache2 Help" on the command line.</p>
318
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
319
<div class="section">
320
<h2><a name="use" id="use">Configuring Apache for NetWare</a></h2>
324
<p>Apache is configured by reading configuration files usually stored
325
in the <code>conf</code> directory. These are the same as files used
326
to configure the Unix version, but there are a few different directives for
327
Apache on NetWare. See the <a href="../">Apache
328
documentation</a> for all the available directives.</p>
330
<p>The main differences in Apache for NetWare are:</p>
334
<p>Because Apache for NetWare is multithreaded, it does not
335
use a separate process for each request, as Apache does on some Unix
336
implementations. Instead there are only threads running: a parent
337
thread, and multiple child or worker threads which handle the requests.</p>
339
<p>Therefore the "process"-management directives are different:</p>
341
<p><code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code> -
342
Like the Unix directive, this controls how many requests
343
a worker thread will serve before exiting. The recommended default,
344
<code>MaxRequestsPerChild 0</code>, causes the thread to continue servicing
345
request indefinitely. It is recommended on NetWare, unless there is some
346
specific reason, that this directive always remain set to <code>0</code>.</p>
348
<p><code class="directive"><a href="../mod/mpm_common.html#startthreads">StartThreads</a></code> -
349
This directive tells the server how many threads it should start initially.
350
The recommended default is <code>StartThreads 50</code>.</p>
352
<p><code class="directive"><a href="../mod/mpm_common.html#minsparethreads">MinSpareThreads</a></code> -
353
This directive instructs the server to spawn additional worker threads
354
if the number of idle threads ever falls below this value. The recommended
355
default is <code>MinSpareThreads 10</code>.</p>
357
<p><code class="directive"><a href="../mod/mpm_common.html#maxsparethreads">MaxSpareThreads</a></code> -
358
This directive instructs the server to begin terminating worker threads
359
if the number of idle threads ever exceeds this value. The recommended
360
default is <code>MaxSpareThreads 100</code>.</p>
362
<p><code class="directive"><a href="../mod/mpm_netware.html#maxthreads">MaxThreads</a></code> -
363
This directive limits the total number of work threads to a maximum
364
value. The recommended default is <code>ThreadsPerChild 250</code>.</p>
366
<p><code class="directive"><a href="../mod/mpm_common.html#threadstacksize">ThreadStackSize</a></code> -
367
This directive tells the server what size of stack to use
368
for the individual worker thread. The recommended default
369
is <code>ThreadStackSize 65536</code>.</p>
373
<p>The directives that accept filenames as arguments must use
374
NetWare filenames instead of Unix names. However, because Apache
375
uses Unix-style names internally, forward slashes must be used
376
rather than backslashes. It is recommended that all rooted file paths
377
begin with a volume name. If omitted, Apache will assume the
378
<code>SYS:</code> volume which may not be correct.</p>
382
<p>Apache for NetWare has the ability to load modules at
383
runtime, without recompiling the server. If Apache is
384
compiled normally, it will install a number of optional
385
modules in the <code>\Apache2\modules</code> directory.
386
To activate these, or other modules, the <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code> directive
387
must be used. For example, to active the status module, use
390
<div class="example"><p><code>
391
LoadModule status_module modules/status.nlm
394
<p>Information on <a href="../mod/mod_so.html#creating">creating loadable
395
modules</a> is also available.</p>
399
<h3><a name="use-add" id="use-add">Additional NetWare specific directives:</a></h3>
404
<li><code class="directive"><a href="../mod/core.html#cgimapextension">CGIMapExtension</a></code> -
405
This directive maps a CGI file extension to a script interpreter.</li>
408
<li><code class="directive"><a href="../mod/mod_nw_ssl.html#securelisten">SecureListen</a></code> -
409
Enables SSL encryption for a specified port.</li>
412
<li><code class="directive"><a href="../mod/mod_nw_ssl.html#nwssltrustedcerts">NWSSLTrustedCerts</a></code> -
413
Adds trusted certificates that are used to create secure connections to proxied servers.</li>
416
<li><code class="directive"><a href="../mod/mod_nw_ssl.html#nwsslupgradeable">NWSSLUpgradeable</a></code> -
417
Allow a connection created on the specified address/port to be upgraded to an SSL connection.</li>
422
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
423
<div class="section">
424
<h2><a name="comp" id="comp">Compiling Apache for NetWare</a></h2>
428
<p>Compiling Apache requires MetroWerks CodeWarrior 6.x or higher. Once
429
Apache has been built, it can be installed to the root of any NetWare
430
volume. The default is the <code>sys:/Apache2</code> directory.</p>
432
<p>Before running the server you must fill out the <code>conf</code>
433
directory. Copy the file <code>HTTPD-STD.CONF</code> from the distribution
434
<code>conf</code> directory and rename it to <code>HTTPD.CONF</code>.
435
Edit the <code>HTTPD.CONF</code> file searching for all <code>@@Value@@</code>
436
markers and replacing them with the appropriate setting. Copy over
437
the <code>conf/magic</code> and <code>conf/mime.types</code> files as well.
438
Alternatively, a complete distribution can be built by including the keyword
439
<code>install</code> when invoking the makefiles.</p>
441
<h3><a name="comp-req" id="comp-req">Requirements:</a></h3>
445
<p>The following development tools are required to build
446
Apache 2.0 for NetWare:</p>
449
<li>Metrowerks CodeWarrior 6.0 or higher with the
450
<a href="http://developer.novell.com/ndk/cwpdk.htm">NetWare PDK 3.0</a>
453
<li><a href="http://developer.novell.com/ndk/libc.htm">NetWare Libraries
454
for C (LibC)</a></li>
456
<li><a href="http://developer.novell.com/ndk/cldap.htm">LDAP Libraries
459
<li><a href="http://www.gzip.org/zlib/">ZLIB Compression Library source code</a></li>
461
<li>AWK utility (awk, gawk or similar). AWK can be downloaded from
462
<a href="http://developer.novell.com/ndk/apache.htm">http://developer.novell.com/ndk/apache.htm</a>.
463
The utility must be found in your windows path and must be named <code>awk.exe</code>.</li>
465
<li>To build using the makefiles, you will need GNU make version 3.78.1 (GMake) available at
466
<a href="http://developer.novell.com/ndk/apache.htm">http://developer.novell.com/ndk/apache.htm</a>.</li>
471
<h3><a name="comp-make" id="comp-make">Building Apache using the NetWare makefiles:</a></h3>
476
<li>Set the environment variable <code>NOVELLLIBC</code> to the
477
location of the NetWare Libraries for C SDK, for example:
478
<div class="example"><p><code>Set NOVELLLIBC=c:\novell\ndk\libc</code></p></div>
481
<li>Set the environment variable <code>METROWERKS</code> to the
482
location where you installed the Metrowerks CodeWarrior compiler,
484
<div class="example"><p><code>Set METROWERKS=C:\Program Files\Metrowerks\CodeWarrior</code></p></div>
485
If you installed to the default location <code>C:\Program
486
Files\Metrowerks\CodeWarrior</code>, you don't need to set this.</li>
488
<li>Set the environment variable <code>LDAPSDK</code> to the
489
location where you installed the LDAP Libraries for C, for example:
490
<div class="example"><p><code>Set LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc</code></p></div>
493
<li>Set the environment variable <code>ZLIBSDK</code> to the
494
location where you installed the source code for the ZLib Library,
496
<div class="example"><p><code>Set ZLIBSDK=D:\NOVELL\zlib</code></p></div>
499
<li>Set the environment variable <code>AP_WORK</code> to the full path of
500
the <code>httpd</code> source code directory.
501
<div class="example"><p><code>Set AP_WORK=D:\httpd-2.0.x</code></p></div>
504
<li>Set the environment variable <code>APR_WORK</code> to the full path of
505
the <code>apr</code> source code directory. Typically <code>\httpd\srclib\apr</code>
506
but the APR project can be outside of the httpd directory structure.
507
<div class="example"><p><code>Set APR_WORK=D:\apr-1.x.x</code></p></div>
510
<li>Set the environment variable <code>APU_WORK</code> to the full path of
511
the <code>apr-util</code> source code directory. Typically <code>\httpd\srclib\apr-util</code>
512
but the APR-UTIL project can be outside of the httpd directory structure.
513
<div class="example"><p><code>Set APU_WORK=D:\apr-util-1.x.x</code></p></div>
516
<li>Make sure that the path to the AWK utility and the GNU make utility
517
(<code>gmake.exe</code>) have been included in the system's
518
<code>PATH</code> environment variable.</li>
520
<li>Download the source code and unzip to an appropriate directory on
521
your workstation.</li>
523
<li>Change directory to <code>\httpd-2.0</code> and build the prebuild utilities
524
by running "<code>gmake -f nwgnumakefile prebuild</code>". This target will create
525
the directory <code>\httpd-2.0\nwprebuild</code> and copy each of the utilities
526
to this location that are necessary to complete the following build steps.
529
<li>Copy the files <code>\httpd-2.0\nwprebuild\GENCHARS.nlm</code> and
530
<code>\httpd-2.0\nwprebuild\DFTABLES.nlm</code> to the <code>SYS:</code> volume of a
531
NetWare server and run them using the following commands:
532
<div class="example"><p><code>
533
SYS:\genchars > sys:\test_char.h<br />
534
SYS:\dftables sys:\chartables.c<br />
538
<li>Copy the files <code>test_char.h</code> and <code>chartables.c</code>
539
to the directory <code>\httpd-2.0\os\netware</code> on the build machine.</li>
541
<li>Change directory to <code>\httpd-2.0</code> and build Apache by running
542
"<code>gmake -f nwgnumakefile</code>". You can create a distribution directory by
543
adding an install parameter to the command, for example:
544
<div class="example"><p><code>gmake -f nwgnumakefile install</code></p></div>
550
<h3><a name="comp-add" id="comp-add">Additional make options</a></h3>
555
<li><code>gmake -f nwgnumakefile</code><p>Builds release versions of all of the
556
binaries and copies them to a <code>\release</code> destination directory.</p></li>
558
<li><code>gmake -f nwgnumakefile DEBUG=1</code><p>Builds debug versions of all of the
559
binaries and copies them to a <code>\debug</code> destination directory.</p></li>
561
<li><code>gmake -f nwgnumakefile install</code><p>Creates a complete Apache
562
distribution with binaries, docs and additional support files in a
563
<code>\dist\Apache2</code> directory.</p></li>
565
<li><code>gmake -f nwgnumakefile prebuild</code><p>Builds all of the prebuild utilities
566
and copies them to the <code>\nwprebuild</code> directory.</p></li>
568
<li><code>gmake -f nwgnumakefile installdev</code><p>Same as install but also creates a
569
<code>\lib</code> and <code>\include</code> directory in the destination directory
570
and copies headers and import files.</p></li>
572
<li><code>gmake -f nwgnumakefile clean</code><p>Cleans all object files and binaries
573
from the <code>\release.o</code> or <code>\debug.o</code> build areas depending on whether
574
<code>DEBUG</code> has been defined.</p></li>
576
<li><code>gmake -f nwgnumakefile clobber_all</code><p>Same as clean and also deletes
577
the distribution directory if it exists.</p></li>
582
<h3><a name="comp-add-env" id="comp-add-env">Additional environment variable options</a></h3>
587
<li>To build all of the experimental modules, set the environment
588
variable <code>EXPERIMENTAL</code>:
589
<div class="example"><p><code>Set EXPERIMENTAL=1</code></p></div>
592
<li>To build Apache using standard BSD style sockets rather than
593
Winsock, set the environment variable <code>USE_STDSOCKETS</code>:
594
<div class="example"><p><code>Set USE_STDSOCKETS=1</code></p></div>
601
<h3><a name="comp-mod_ssl" id="comp-mod_ssl">Building mod_ssl for the NetWare platform</a></h3>
605
<p>By default Apache for NetWare uses the built-in module
606
<code class="module"><a href="../mod/mod_nw_ssl.html">mod_nw_ssl</a></code> to provide SSL services. This module
607
simply enables the native SSL services implemented in NetWare OS
608
to handle all encryption for a given port. Alternatively, mod_ssl
609
can also be used in the same manner as on other platforms.</p>
611
<p>Before mod_ssl can be built for the NetWare platform, the OpenSSL
612
libraries must be provided. This can be done through the following
616
<li>Download the latest NetWare patch for OpenSSL from the
617
<a href="http://www.openssl.org/contrib/">OpenSSL Contribution</a>
620
<li>Download the corresponding OpenSSL source code from the
621
<a href="http://www.openssl.org/source/">OpenSSL Source</a>
624
<li>At the root of the OpenSSL source directory, apply the NetWare
625
patch using the "patch" utility, for example:
626
<div class="example"><p><code>patch -p 1 -i netwarepatch-0.9.7g.diff</code></p></div></li>
628
<li>Edit the file <code>NetWare/set_env.bat</code> and modify any
629
tools and utilities paths so that they correspond to your build
632
<li>From the root of the OpenSSL source directory, run the following
634
<div class="example"><p><code>
635
Netware/set_env netware-libc<br />
636
Netware/build netware-libc
637
</code></p></div></li>
639
<li>Before building Apache, set the environment variable
640
<code>OSSLSDK</code> to the full path to the root of the openssl
641
source code directory.
642
<div class="example"><p><code>Set OSSLSDK=d:\openssl-0.9.7x</code></p></div></li>
649
<div class="bottomlang">
650
<p><span>Available Languages: </span><a href="../en/platform/netware.html" title="English"> en </a> |
651
<a href="../ko/platform/netware.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
652
</div><div id="footer">
653
<p class="apache">Copyright 2006 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
654
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div>
b'\\ No newline at end of file'
added
removed
docs/manual/platform/netware.html.en
