From: Ken Coar Date: Fri, 8 Jan 1999 23:13:29 +0000 (+0000) Subject: The semi-occasional partial cleaning-up of the HTML.. X-Git-Tag: 1.3.4~3 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2133186f4f6a05b4d7963f546b9bff3812630c93;p=apache The semi-occasional partial cleaning-up of the HTML.. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@82618 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/install-tpf.html b/docs/manual/install-tpf.html index d902e3496f..9545a7a7c1 100644 --- a/docs/manual/install-tpf.html +++ b/docs/manual/install-tpf.html @@ -1,109 +1,121 @@ - - -Installing Apache on TPF - + + +Installing Apache on TPF + - -

Installing the Apache 1.3 HTTP Server on TPF

-[ Setup - | Compilation - | Installation - | VisualAge ] - -

-
+ +

+ Installing the Apache 1.3 HTTP Server on TPF +

+[ Setup + | Compilation + | Installation + | VisualAge ] + +

+
-

This document outlines the steps needed to install Apache onto a TPF system. -

-You should first read htdocs/manual/readme-tpf.html +

+You should first read +htdocs/manual/readme-tpf.html for basic information on the port of Apache to TPF including required PUT level and supported functions & modules. -

- -

Setup

-Due to the use of EBCDIC on MVS OS/390 Open Edition (later referred to simply as +

Setup

+Due to the use of EBCDIC on MVS OS/390 Open Edition +(later referred to simply as "Open Edition"), we've found that the most reliable method for loading Apache onto your system is to unzip and tar the distribution -file on your PC, and then copy the extracted files to Open Edition via an NFS client +file on your PC, and then copy the extracted files to Open Edition +via an NFS client capable of transferring the data in EBCDIC format. -

+

Before moving the distribution to an Open Edition environment, verify that the NFS drive will transfer the filenames with upper/lower case preserved. -

+

Since Open Edition is not the ultimate destination of the files, -the only required files and subdirectories that need to be moved to Open Edition +the only required files and subdirectories that need to be moved to +Open Edition are in /src. -

-WARNING: +

+WARNING: If you are using a product such as WinZip on your PC, verify that -the "TAR File Smart CR/LF Conversion" option is NOT checked. +the "TAR File Smart CR/LF Conversion" option is NOT checked. You can find this in WinZip under Options, Configuration. Since you had to tar and unzip the file to read this document, you need to re-tar and -unzip if the CR/LF option was checked. This will save you lots of headaches later on. -

-WARNING: +

+WARNING: Editing files on a PC before moving them to Open Edition may result -in the loss/addition of unprintable characters. Files of concern include shell -scripts and src/Configuration. The most common problems are with tab characters +in the loss/addition of unprSintable characters. Files of concern include shell +scripts and src/Configuration. The most common problems are with +tab characters and CR/LF characters. Most editors will handle the CR/LF problem correctly but none seem to handle tab characters. If you need to edit files, edit them in a UNIX editor such as vi or emacs. -

- -

Compilation

Apache supports the notion of "optional modules". However, the server has to know which modules are compiled into it. In order for those modules to be effective, it is necessary to generate a short bit of code ("modules.c") which simply has a list of them. If you are using the make and Configure utility, "modules.c" will be created for you. -

+

The provided scripts assume a c89 compiler and have only been tested on an Open Edition environment. If you are using a platform other that Open Edition you may need to modify src/os/tpf/TPFExport and src/Configure to match your environment. -

+

Note that UNIX/Open Edition commands in this section are shown in -bold, +bold, are case sensitive, and must be made from the "src" directory. -

-

Overlay src/Configuration with src/Configuration.tmpl: - cp Configuration.tmpl Configuration -

-
Edit src/Configuration. It contains the list and settings +
+
1. Overlay src/Configuration with src/Configuration.tmpl: + cp Configuration.tmpl Configuration +
  
  +
2. Edit src/Configuration. It contains the list and settings of various "Rules" and an additional section at the bottom that determines which modules to compile: -
  
  -
  1. Adjust the Rules and EXTRA_CFLAGS|LIBS|LDFLAGS|INCLUDES +
    
    +
    1. Adjust the Rules and EXTRA_CFLAGS|LIBS|LDFLAGS|INCLUDES if you feel so inclined. -
      
      -
    2. Comment out (by preceding the line with a "#") lines corresponding +
      
      +
    3. Comment out (by preceding the line with a "#") lines corresponding to those modules you DO NOT wish to include. At present the following modules MUST be commented out as they are not yet supported on TPF: mod_actions, mod_auth, mod_cgi, mod_env, mod_include, & mod_status. -
      
      -
    4. Uncomment (by removing the initial "#", if present) lines +
      
      +
    5. Uncomment (by removing the initial "#", if present) lines corresponding to those optional modules you wish to include or add new lines corresponding to any custom modules you have written. - The htdocs/manual/readme-tpf.html + The htdocs/manual/readme-tpf.html document lists the modules that have been tested on TPF. -
    -
    -
  2. Set the TPF environment variables: - . os/tpf/TPFExport -
    +
  +
  +
3. Set the TPF environment variables: + . os/tpf/TPFExport +
  (The initial period and blank on the command are required to ensure the environment variables exist beyond the scope of the shell script.) This script will set the environment variables required to compile the @@ -111,14 +123,14 @@ are case sensitive, and must be made from the "src" directory. installation, in particular, the system include file directories. The system include files must reside on your Open Edition system in the appropriate file structure similar to /usr/include and /usr/include/sys. - DO NOT modify the TPF=YES export variable. If this is changed, the - "Configure" script will not recognize TPF. -
  
  -
4. Run the "Configure" script: - Configure -
  + DO NOT modify the TPF=YES export variable. If this is + changed, the "Configure" script will not recognize TPF. +
  
  +
5. Run the "Configure" script: + Configure +
  The output will look something like this... -
```
+             Using config file: Configuration
       Creating Makefile
        + configured for TPF platform
@@ -134,134 +146,131 @@ are case sensitive, and must be made from the "src" directory.
       Creating Makefile in modules/standard
       Creating Makefile in modules/example
       $ _
-      
+      
```
  This generates modules.c and new versions of the Makefiles. -
  
  - If you want to maintain multiple configurations, you can say, e.g., -
  - Configure -file Configuration.ai -
  -
```
+    


+    If you want to maintain multiple configurations, you can
+    say, e.g.,
+    

+    Configure -file Configuration.ai
+    

+             Using config file: Configuration.ai
       Creating Makefile
        + configured for <whatever> platform
        + setting C compiler to <whatever>
       et cetera
-      
+      
```
  - If you receive an error such as "Configure 146: FSUM7351 not found" + If you receive an error such as "Configure 146: FSUM7351 not found" the most likely explanation is that one or more of the make related files were edited on a non-UNIX platform, corrupting the end-of-line marks. Verify that lines ending with "\" in the flagged file do not have trailing spaces. Using the vi editor and the sample error above as an example... -
```
-            pull up the flagged file:       vi Configure
-            turn on punctuation:            :set list
-            go to the line in question:     146G
-               or find a line with a "\":   /\\
```
  - The end of line should display as "\$". If it is displayed as - "\ $" (with a blank between \ and $) then you should revert to the +
```
+            pull up the flagged file:       vi Configure
+            turn on punctuation:            :set list
+            go to the line in question:     146G
+               or find a line with a "\":   /\\
```
  + The end of line should display as "\$". If it is displayed as + "\ $" (with a blank between \ and $) then you should revert to the distributed version of the file and make the site-specific changes again using a UNIX compatible editor such as vi or emacs. Then try the Configure command again. -
```
            close the file:                 :q  (or 
+    
            close the file:                 :q  (or 
 
-:quit!)
-Now compile the programs: make

+:quit!)
```
  +
6. Now compile the programs: make
  The modules placed in the Apache distribution are the ones that have been tested and are used regularly by various members of the Apache development group. Additional modules contributed by members or third parties with specific needs or functions are available at - http://www.apache.org/dist/contrib/modules/. + http://www.apache.org/dist/contrib/modules/. There are instructions on that page for linking these modules into the core Apache code. -
  
  +
  
  If during compilation you get a warning about a missing 'regex.h', set - WANTHSREGEX=yes in the src/Configuration file and start back at the - Configure step. -
-
+ WANTHSREGEX=yes in the src/Configuration file and start back at the + Configure step. +

- -

Installation

After compilation, you will have all the object files required to build an + +
Installation
+
1. After compilation, you will have all the object files required to build an "httpd" loadset. The next step is to link the object files and create a loadset to be stored in a PDS. Sample JCL for linking and loadsets has been included in src/os/tpf/samples as "linkdll.jcl" and "loadset.jcl". You can submit these jobs from CMS or directly from Open Edition if you have the proper authority. After - the jobs have completed, you can ZOLDR LOAD them to your TPF system. -
  
  - NOTE: The mod_xxx.o files in the linkdll.jcl file must correspond to the - mod_xxx.o lines in the src/Configuration file. -
  
  -
2. + the jobs have completed, you can ZOLDR LOAD them to your TPF system. +
  
  + NOTE: The mod_xxx.o files in the linkdll.jcl file must correspond to the + mod_xxx.o lines in the src/Configuration file. +
  
  +
3. Apache requires a configuration file to initialize itself during activation. (Previously three configuration files were used.) Copy the distribution version, /conf/httpd.conf-dist, to /conf/httpd.conf and then edit the /conf/httpd.conf copy with your site specific information. This first release of Apache for TPF only runs under the "inetd" model so you - must change ServerType from standalone - to inetd. -
  
  + must change ServerType from standalone + to inetd. +
  
  General documentation for Apache is located at - http://www.apache.org/docs/ + http://www.apache.org/docs/ and in the HTML pages included with this distribution under the /htdocs/manual directory. -
  
  -
4. On TPF activate ZCLAW and update INETD using ZINET entries, the common case: -
  
  -
```
+  


+On TPF activate ZCLAW and update INETD using ZINET entries, the common case:
+    


+         ZINET ADD S-TFTP   PGM-CTFT PORT-69 PROTOCOL-UDP MODEL-NOWAIT
-    ZINET ADD S-APACHE PGM-pppp PORT-80 PROTOCOL-TCP MODEL-NOWAIT
-  Please refer to IBM Transaction Processing Facility Transmission Control
-  Protocol/Internet Protocol Version 4 Release 1 for more information
+    ZINET ADD S-APACHE PGM-pppp PORT-80 PROTOCOL-TCP MODEL-NOWAIT
```
  + Please refer to IBM Transaction Processing Facility Transmission Control + Protocol/Internet Protocol Version 4 Release 1 for more information on ZCLAW, INETD, and TFTP. -
  
  -
5. Prior to sending a request to your Apache server from a browser, +
  
  +
6. Prior to sending a request to your Apache server from a browser, TFTP the configuration file, log, icons and web pages to your TPF system. A typical directory structure for Apache is as follows: -
```
     /usr/local/apache/conf
+     /usr/local/apache/conf
      /usr/local/apache/logs
      /usr/local/apache/icons
-     /usr/local/apache/htdocs
+     /usr/local/apache/htdocs
```
  The logs directory must exist in order to avoid an - fopen error while running Apache. TFTP an empty file into + fopen error while running Apache. TFTP an empty file into the logs subdirectory to create it. All gif, jpg, and zip files should be TFTP'd as binary; conf files and html pages should be TFTP'd as text. -
- -
Compiling with VisualAge TPF
-
+

+ +

Compiling with VisualAge TPF

It is not required that "make" be used to compile Apache for TPF: Individual programs may be compiled using IBM's VisualAge TPF product. This is particularly useful when compiling selected programs for the Debug Tool. -

+

The following VisualAge compile settings are required: -

"DEFINE - Define preprocessor macro name(s)" must include - TPF, CHARSET_EBCDIC, _POSIX_SOURCE, and - USE_HSREGEX -

-
"LSEARCH - Path for user include files" must include - ../src/include and ../src/os/tpf -

-
"DLL - Generate DLL code" must be checked -

-
"LONGNAME - Support long names" must be checked -

-[ top - | Setup - | Compilation - | Installation - | VisualAge ] - +

"DEFINE - Define preprocessor macro name(s)" must include + TPF, CHARSET_EBCDIC, _POSIX_SOURCE, and + USE_HSREGEX +

+
"LSEARCH - Path for user include files" must include + ../src/include and ../src/os/tpf +

+
"DLL - Generate DLL code" must be checked +

+
"LONGNAME - Support long names" must be checked +

+[ top + | Setup + | Compilation + | Installation + | VisualAge ] + - - + + diff --git a/docs/manual/mod/mod_mime.html b/docs/manual/mod/mod_mime.html index 9ac03dd8e9..eb8e2be663 100644 --- a/docs/manual/mod/mod_mime.html +++ b/docs/manual/mod/mod_mime.html @@ -51,7 +51,7 @@ copies may still be used by a client or proxy, with the previous headers.

Files with Multiple Extensions

Files can have more than one extension, and the order of the -extensions is normally irrelevant. For example, if the file +extensions is normally irrelevant. For example, if the file welcome.html.fr maps onto content type text/html and language French then the file welcome.fr.html will map onto exactly the same information. The only exception to this is if an diff --git a/docs/manual/platform/readme-tpf.html b/docs/manual/platform/readme-tpf.html index 3cb36250df..2e9161b1aa 100644 --- a/docs/manual/platform/readme-tpf.html +++ b/docs/manual/platform/readme-tpf.html @@ -1,206 +1,206 @@ - - -The Apache TPF Port - - - -

Overview of the Apache TPF Port

-[ Configuration Files - | Auto Generated Files - | What's Available - | Porting Notes ] - -

-
- -

+ + +The Apache TPF Port + + + +

Overview of the Apache TPF Port

+[ Configuration Files + | Auto Generated Files + | What's Available + | Porting Notes ] + +

+
+ +

This version of Apache includes changes allowing it to run on IBM's EBCDIC-based - TPF + TPF (Transaction Processing Facility) operating system. Unless otherwise noted TPF version 4.1 PUT08 and APAR PJ25589 are required. -

- Refer to htdocs/manual/install-tpf.html +

+ Refer to htdocs/manual/install-tpf.html for step-by-step installation instructions. -

+

As this is the first cut at making Apache run on TPF, performance tuning has not been done. -

- This port builds upon the EBCDIC changes +

+ This port builds upon the EBCDIC changes previously made to Apache. -
-

+
+

- -

Apache Configuration Files

+ +

Apache Configuration Files

The distributed configuration files (httpd.conf-dist and mime.types, both located in the conf subdirectory) work on TPF with only a couple of operating system specific changes - to httpd.conf:
-

ServerType needs to be "inetd" since TPF does not yet support + to httpd.conf:
+
- ServerType needs to be "inetd" since TPF does not yet support "standalone" mode. -
- Performance considerations may dictate setting KeepAlive to "Off" +
- Performance considerations may dictate setting KeepAlive to "Off" (the default is "On") or lowering the Timeout value from the default 300 seconds (5 minutes) in order to reduce the number of active ECBs on your system. -
-
+

- -

What's Available in this Version

+ +

What's Available in this Version

(The Apache organization provides - online documentation + online documentation describing the various modules and components of the server.) -

Components/modules tested on TPF:

- -

alloc.c -
ap_cpystrn.c -
ap_fnmatch.c -
ap_signal.c -
ap_slack.c -
ap_snprintf.c -
buff.c -
buildmark.c -
ebcdic.c -
http_config.c -
http_core.c -
http_log.c -
http_main.c -
http_protocol.c -
http_request.c -
http_vhost.c * -
mod_access.c -
mod_alias.c -
mod_asis.c -
mod_autoindex.c -
mod_cern_meta.c -
mod_dir.c -
mod_example.c -
mod_expires.c -
mod_headers.c -
mod_imap.c -
mod_info.c -
mod_log_agent.c -
mod_log_config.c -
mod_log_referer.c -
mod_mime.c -
mod_negotiation.c -
mod_setenvif.c -
mod_speling.c -
mod_userdir.c -
mod_usertrack.c -
os.c -
os-inline.c -
regular expression parser -
util.c -
util_date.c -
util_uri.c -

Components/modules tested on TPF:

+ +

alloc.c +
ap_cpystrn.c +
ap_fnmatch.c +
ap_signal.c +
ap_slack.c +
ap_snprintf.c +
buff.c +
buildmark.c +
ebcdic.c +
http_config.c +
http_core.c +
http_log.c +
http_main.c +
http_protocol.c +
http_request.c +
http_vhost.c * +
mod_access.c +
mod_alias.c +
mod_asis.c +
mod_autoindex.c +
mod_cern_meta.c +
mod_dir.c +
mod_example.c +
mod_expires.c +
mod_headers.c +
mod_imap.c +
mod_info.c +
mod_log_agent.c +
mod_log_config.c +
mod_log_referer.c +
mod_mime.c +
mod_negotiation.c +
mod_setenvif.c +
mod_speling.c +
mod_userdir.c +
mod_usertrack.c +
os.c +
os-inline.c +
regular expression parser +
util.c +
util_date.c +
util_uri.c +

Please keep in mind that some major pieces are not yet in place including standalone mode, pipes, password/group files, CGI scripts, and MD5 support. -
- -
+
+ +
* virtual hosting requires TPF version 4.1 PUT09 -

Components/modules not (yet?) supported on TPF:

- -

htpasswd.c -
md5c.c -
mod_actions.c -
mod_auth.c -
mod_auth_anon.c -
mod_cgi.c -
mod_digest.c -
mod_env.c -
mod_include.c -
mod_mime_magic.c -
mod_proxy.c -
mod_rewrite.c -
mod_status.c -
mod_unique_id.c -
proxy_cache.c -
proxy_connect.c -
proxy_ftp.c -
proxy_http.c -
proxy_util.c -
rfc1413.c -
util_md5.c -
util_script.c -

- -

Components/modules that don't apply or that probably won't ever be available on TPF:

- -

gen_test.char.c -
gen_uri_delims.c -
mod_auth_db.c -
mod_auth_dbm.c -
mod_auth_db.module -
mod_mmap_static.c -
mod_so.c -

- - -

Porting Notes

Changes made due to differences between UNIX and - TPF's process models:

Signals: On TPF a signal that is sent to a process +
Components/modules not (yet?) supported on TPF:
+ +
- htpasswd.c +
- md5c.c +
- mod_actions.c +
- mod_auth.c +
- mod_auth_anon.c +
- mod_cgi.c +
- mod_digest.c +
- mod_env.c +
- mod_include.c +
- mod_mime_magic.c +
- mod_proxy.c +
- mod_rewrite.c +
- mod_status.c +
- mod_unique_id.c +
- proxy_cache.c +
- proxy_connect.c +
- proxy_ftp.c +
- proxy_http.c +
- proxy_util.c +
- rfc1413.c +
- util_md5.c +
- util_script.c +
+ +
Components/modules that don't apply or that probably won't ever be available on TPF:
+ +
- gen_test.char.c +
- gen_uri_delims.c +
- mod_auth_db.c +
- mod_auth_dbm.c +
- mod_auth_db.module +
- mod_mmap_static.c +
- mod_so.c +
+ + +
Porting Notes
+
+
Changes made due to differences between UNIX and + TPF's process models:
+
- Signals: On TPF a signal that is sent to a process remains unhandled until the process explicitly requests that signals - be handled using the tpf_process_signals() function. + be handled using the tpf_process_signals() function. Additionally, the default action for an alarm on TPF is to take an OPR-7777 dump and exit. (On UNIX the default is the equivalent - of exit() with no dump taken.) + of exit() with no dump taken.) These differences necessitated a few modifications: -
  
  -
  - bypass the use of ap_block_alarms() & - ap_unblock_alarms() -
  - add tpf_process_signals() calls -
  - add select() calls in buff.c to prevent blocking. -
  -
  -
- -
Find that function...
-
Some simple functions & definitions needed to be added - on TPF, such as FD_SET(). +

+
- bypass the use of ap_block_alarms() & + ap_unblock_alarms() +
- add tpf_process_signals() calls +
- add select() calls in buff.c to prevent blocking. +
+
+

+ +

Find that function...

Some simple functions & definitions needed to be added + on TPF, such as FD_SET(). We've put these in src/os/tpf/os.h for now. -

EBCDIC changes:

TPF-specific conversion tables between US-ASCII and +

EBCDIC changes:

TPF-specific conversion tables between US-ASCII and EBCDIC (character set IBM-1047 to be exact) were created and put into ebcdic.c in the src/os/tpf directory. -

Miscellaneous, minor changes:

Various minor changes (such as casting) were made due to +

Miscellaneous, minor changes:

Various minor changes (such as casting) were made due to differences in how some functions are implemented on TPF. -

Temporary changes:

Lastly, we needed to bypass sections of Apache processing +

Temporary changes:

Lastly, we needed to bypass sections of Apache processing since this first cut for TPF doesn't include Standalone mode, pipes, forking, et cetera. -

- -

-[ top - | Configuration Files - | Auto Generated Files - | What's Available - | Porting Notes ] - - - - +

+ +

+[ top + | Configuration Files + | Auto Generated Files + | What's Available + | Porting Notes ] + + + + diff --git a/docs/manual/suexec.html b/docs/manual/suexec.html index 237fe86e67..3d8623df04 100644 --- a/docs/manual/suexec.html +++ b/docs/manual/suexec.html @@ -309,25 +309,25 @@ for Apache 1.3 with the AutoConf-style interface (APACI). activated by default. At least one --suexec-xxxxx option has to be provided together with the --enable-suexec option to let APACI accept your request for using the suEXEC feature. -

--suexec-caller=UID +

--suexec-caller=UID

The username under which Apache normally runs. This is the only user allowed to execute this program. -

--suexec-docroot=DIR +

--suexec-docroot=DIR

Define as the DocumentRoot set for Apache. This will be the only hierarchy (aside from UserDirs) that can be used for suEXEC behavior. The default directory is the --datadir value with - the suffix "/htdocs", e.g. if you configure with + the suffix "/htdocs", e.g. if you configure with "--datadir=/home/apache" the directory "/home/apache/htdocs" is used as document root for the suEXEC wrapper. -

--suexec-logfile=FILE +

--suexec-logfile=FILE

This defines the filename to which all suEXEC transactions and errors are logged (useful for auditing and debugging purposes). By default the logfile is named "suexec_log" and located in your standard logfile directory (--logfiledir). -

--suexec-userdir=DIR +

--suexec-userdir=DIR

Define to be the subdirectory under users' home directories where suEXEC access should be allowed. All executables under this directory @@ -346,15 +346,15 @@ for Apache 1.3 with the AutoConf-style interface (APACI). all reside in one parent directory; then name that parent directory here. If this is not defined properly, "~userdir" cgi requests will not work! -

--suexec-uidmin=UID +

--suexec-uidmin=UID

Define this as the lowest UID allowed to be a target user for suEXEC. For most systems, 500 or 100 is common. Default value is 100. -

--suexec-gidmin=GID +

--suexec-gidmin=GID

Define this as the lowest GID allowed to be a target group for suEXEC. For most systems, 100 is common and therefore used as default value. -

--suexec-safepath=PATH +

--suexec-safepath=PATH

Define a safe PATH environment to pass to CGI executables. Default value is "/usr/local/bin:/usr/bin:/bin". @@ -407,7 +407,7 @@ directory (default is "/usr/local/apache/sbin/suexec"). If Apache finds a properly configured suEXEC wrapper, it will print the following message to the error log:

-    [notice] suEXEC mechanism enabled (wrapper: /path/to/suexec)
+    [notice] suEXEC mechanism enabled (wrapper: /path/to/suexec)

If you don't see this message at server startup, the server is most likely not finding the wrapper program where it expects it, or the diff --git a/docs/manual/suexec.html.en b/docs/manual/suexec.html.en index 237fe86e67..3d8623df04 100644 --- a/docs/manual/suexec.html.en +++ b/docs/manual/suexec.html.en @@ -309,25 +309,25 @@ for Apache 1.3 with the AutoConf-style interface (APACI). activated by default. At least one --suexec-xxxxx option has to be provided together with the --enable-suexec option to let APACI accept your request for using the suEXEC feature. -

--suexec-caller=UID +

--suexec-caller=UID

The username under which Apache normally runs. This is the only user allowed to execute this program. -

--suexec-docroot=DIR +

--suexec-docroot=DIR

--suexec-logfile=FILE +

--suexec-logfile=FILE

--suexec-userdir=DIR +

--suexec-userdir=DIR

--suexec-uidmin=UID +

--suexec-uidmin=UID

Define this as the lowest UID allowed to be a target user for suEXEC. For most systems, 500 or 100 is common. Default value is 100. -

--suexec-gidmin=GID +

--suexec-gidmin=GID

Define this as the lowest GID allowed to be a target group for suEXEC. For most systems, 100 is common and therefore used as default value. -

--suexec-safepath=PATH +

--suexec-safepath=PATH

-    [notice] suEXEC mechanism enabled (wrapper: /path/to/suexec)
+    [notice] suEXEC mechanism enabled (wrapper: /path/to/suexec)

If you don't see this message at server startup, the server is most likely not finding the wrapper program where it expects it, or the

Installing the Apache 1.3 HTTP Server on TPF

+ Installing the Apache 1.3 HTTP Server on TPF +

Setup

Setup

Compilation

Compilation

Installation

Installation

Compiling with VisualAge TPF

Compiling with VisualAge TPF

Files with Multiple Extensions

Overview of the Apache TPF Port

Overview of the Apache TPF Port

Apache Configuration Files

Apache Configuration Files

What's Available in this Version

What's Available in this Version

Components/modules tested on TPF:

Components/modules tested on TPF:

Components/modules not (yet?) supported on TPF:

Components/modules that don't apply or that probably won't ever be available on TPF:

Porting Notes

Changes made due to differences between UNIX and - TPF's process models:

Components/modules not (yet?) supported on TPF:

Components/modules that don't apply or that probably won't ever be available on TPF:

Porting Notes

Changes made due to differences between UNIX and + TPF's process models:

Find that function...

Find that function...

EBCDIC changes:

EBCDIC changes:

Miscellaneous, minor changes:

Miscellaneous, minor changes:

Temporary changes:

Temporary changes: