Apache Web Server for SCO OpenServer 5.0 Release and Installation Notes

System requirements
Installing and removing Apache
Installing Apache
Removing Apache
Installation directory
Existing server configuration files and content
Starting and stopping the Apache web server
Port 80 default server, and interactions with Netscape FastTrack
Documentation notes
Apache and Microsoft FrontPage
Managing DBM and DB authorization files

Apache for OpenServer 5.0 is a robust, full-featured HTTP web server derived from the Apache Project open source server.

The following notes apply only to the supported Apache web server installation, Apache release 1.3.9, on OpenServer 5.0 systems. For notes on other Apache releases, specifically the Skunkware release of Apache, consult the relevant Skunkware documentation.

System requirements

Apache software
Apache documentation

Installing and removing Apache

Installing Apache

To install the package from downloaded files:

Log in as root.
Download the volume image VOL.000.000 to an installation directory; for example, /tmp.
Run the custom(ADM) command, by entering custom, or by selecting Software Manager from within scoadmin(ADM).
Select Software->Install New
When prompted for the host from which to install, select the local system
Custom will then ask for the media device. Select Media Images from the pulldown list.
Enter the directory containing the VOL.000.000 file as the Image Directory; for example, /tmp.
Custom will now allow you to select what parts of the product to install. By default, it will install the entire product. You many however elect to install just the runtime portion of the product, or just the documentation portion.
Press Install to begin the installation.
When you have completed the installation, select Host->Exit.

Removing Apache

To remove a layered product or patch, use custom(ADM).

See your OpenServer 5.0 documentation for details.

Installation directory

The Apache server root directory is /usr/internet/apache. In this directory you will find the following subdirectories:

/bin

Apache executable programs

/cgi-bin

Location for CGI-bin gateway programs; this directory and programs in it are created on installation if no such directory already exists, otherwise, the existing files are left in place

/cgi-bin-default

The source for a cgi-bin directory if none exists on installation

/conf

Apache configuration files

/htdocs

Location for HTML content files; this directory and files in it are created on installation if no such directory already exists, otherwise, the existing files are left in place

/htdocs-default

The source for an htdocs directory if none exists on installation

/icons

Images used by Apache when creating HTML pages, typically directory indexes

/include

C-language header files for Apache data structures

/libexec

Dynamically loadable .so files

/libextra

Additional libraries used when building Apache

/logs

Default location of the server access and error log files

/man

Nroff format manual pages for the server and various support utilities

/proxy

Caching directory for the Apache proxy module

Existing server configuration files and content

On installation, Apache will preserve any existing configuration files it finds, renaming them to files with a .bak extension.

If existing /htdocs and /cgi-bin directories are found on the system, the Apache installation will not install its own web server content. Otherwise, it builds up a default set of content from the /htdocs-default and /cgi-bin-default directories.

Starting and stopping the Apache web server

The normal way to start an Apache web server is using the apachectl script; this script is provided in the /bin subdirectory of the Apache installation.

As an alternative, the /etc/apache script is provided. This script also allows the server to be enabled to start on system boot. See the apache(APACHE) manual page for details of how to use this script.

Port 80 default server, and interactions with Netscape FastTrack

By default, Apache creates a port 80 web server instance, and creates some default server content if none exists already. This server runs as user nouser, and serves documents from /usr/internet/apache/htdocs.

If the Netscape FastTrack port 80 server is already running on the system, the Apache port 80 server will fail to start, and log the following type of message to its error log file:

[crit] (125)Address already in use: make_sock: could not bind to port 80

In this case, either stop, or even disable, the FastTrack server before starting Apache, or move one or the other of the servers to a different port.

NOTE: On OpenServer 5.0, the Netscape FastTrack port 80 server is usually enabled to start on boot. To prevent this from happening, you can execute the following commands, as root:

cd /usr/internet/ns_httpd/httpd-80
./stop
mv start old.start
mv stop old.stop

To disable all instances of Netscape FastTrack and the Netscape Administration server, execute the following commands, as root:

cd /etc/rc2.d
./S90fasttrack stop
mv S90fasttrack old.S90fasttrack

To re-enable the servers, reverse these operations.

In general, both Apache and Netscape FastTrack can run together on a single system, providing that they are not trying to listen on the same network port or ports.

Documentation notes

The manual pages for the main Apache server and its supporting programs are built into SCOhelp. Ensure that you have installed the documentation component of the product (included in the full product if selected in custom(ADM)) to enable this feature.

The following manual pages are available:

apache, ab, apachectl, apxs, dbmmanage, htdigest, htpasswd, httpd, logresolve, rotatelogs, and suexec

You can access these pages with the man(C) command when the documentation component of the product is installed.

NOTE: The main Apache User's Guide, and other server documentation that is not simple manual pages, is not integrated into SCOhelp. This documentation is however served by the default port 80 web server instance on installation. If you have disabled the default port 80 server, or replaced the content with your own files, you can still access the documentation by pointing a browser at the local files in

file:/usr/internet/apache/htdocs-default/manual

Alternatively, you can access the Apache documentation directly from the Apache organization, at http://apache.org.

Apache and Microsoft FrontPage

This release of Apache contains the FrontPage 'glue' module mod_frontpage.c. However, this is not the complete FrontPage product; this module contains only the server redirections necessary to allow it to work with a FrontPage installation.

On installation, if Apache determines that FrontPage is not present (that is, no directory /usr/local/frontpage exists), this FrontPage module is automatically disabled by default in the Apache httpd.conf configuration file.

The mod_frontpage module supplied with this release should function with both FrontPage 98 and FrontPage 2000.

Managing DBM and DB authorization files

DB and DBM are two distinct and complementary file formats for user authentication databases in Apache. You may choose to use either to create an authorization database for the server, and depending on which you choose, you will need to make the corresponding configuration changes for the server.

The standard Apache tool for managing DBM and DB authentication files is dbmmanage(APACHE). In this release, dbmmanage(APACHE) will work only if you have installed a version of Perl (for example, from Skunkware) on your system, and even then is only capable of managing DBM format authorization files.

To manage DB and DBM format authorization files, two small additional tools, dbfile and dbmfile, are provided. These tools may be found in the /usr/internet/apache/bin directory. The behave identically with respect to command line flags and input file format; the only difference is that one manages DB format files, and the other DBM format files.

DB format files are created exactly as specified by the argument to dbfile. DBM format files are actually pairs of files, having the extensions .pag and .dir.

The dbfile and dbmfile programs create or update an authorization database from a list of usernames and encrypted passwords that they reads from standard input (one pair per line, separated by whitespace). You can, for example, convert an existing .htpasswd authorization file into a DB format file called authfile.db, using the following command:

awk -F: '{ print $1 " " $2 }' < .htpasswd | \
/usr/internet/apache/bin/dbfile authfile.db

Input for dbfile and dbmfile can also be prepared manually, or using other system tools. If an input line contains a username only, that entry is deleted from the database. If the input line contains both a username and an encrypted password, that entry is either appended to the database, or used to replace the password if an entry for that username already exists.

The -d option to dbfile and dbmfile allows you to view the contents of the database, by writing it to standard output. For example, to convert authfile.db from DB format into DBM format (files authfile.pag and authfile.dir):

/usr/internet/apache/bin/dbfile -d authfile.db | \
/usr/internet/apache/bin/dbmfile authfile

There is no separate documentation for the dbfile and dbmfile utilities.

More information on the DB database file format may be obtained from http://www.sleepycat.com.

Software:	SCO OpenServer 5.0.4, 5.0.5, or greater
RAM:	>64MB
Disk Space:	4MB free disk space