Preface

The Software Release Bulletin: Apache Web Server with PHP for OpenVOS, Release 7.0 (R466) documents the installation of the Apache Web Server with PHP for OpenVOS. This manual describes the OpenVOS implementation of the Apache Web Server with PHP. See Related Manuals for a list of documents that provide detailed information about the Apache Web Server and PHP (PHP stands for PHP: Hypertext Preprocessor).

This manual is intended for system administrators; however, some of the information discussed in this manual may interest application designers, developers, and end users.

Manual Version

This manual is a revision. In this revision, information throughout the manual has been updated to support Apache Web Server with PHP for OpenVOS, Release 7.0. Change bars, which appear in the margin, note the specific changes to text since the previous publication of this manual.

Related Manuals

See the following Stratus manuals for information about basic OpenVOS administrative procedures.

  • OpenVOS System Administration: Administering and Customizing a System 
  • OpenVOS System Administration: Starting Up and Shutting Down a Module or System 
  • OpenVOS System Administration: Registration and Security 
  • OpenVOS System Administration: Configuring a System 

See the following Stratus manuals for additional OpenVOS information.

  • OpenVOS Commands Reference Manual 
  • OpenVOS Standard C Reference Manual 
  • GNU Tools for OpenVOS: User's Guide 
  • Software Release Bulletin: OpenVOS GNU Tools 
  • Software Release Bulletin: Internet Security Pack for OpenVOS, Release 5.0 
  • OpenVOS Installation Guide 

See the following Stratus manuals for information about OpenVOS POSIX.

  • OpenVOS POSIX.1 Reference Guide —A Stratus-supplied guide that includes user-related information about the POSIX.1 product.
  • OpenVOS POSIX.1: Conformance Guide —A Stratus-supplied document that details the implementation differences between OpenVOS POSIX.1 and the POSIX.1 Standard.

See also the following third-party documentation:

Notation Conventions

This manual uses the following notation conventions.

Warnings, Cautions, Notices, and Notes

Warnings, cautions, notices, and notes provide special information and have the following meanings:

Warning: A warning indicates a hazardous situation that, if not avoided, could result in death or serious injury.
Avertissement: Un avertissement indique une situation dangereuse qui, si pas évitée, pourrait entraîner la mort ou des blessures graves.
Caution: A caution indicates a hazardous situation that, if not avoided, could result in minor or moderate injury.
Mise En Garde: Une mise en garde indique une situation dangereuse qui, si pas évitée, pourrait entraîner des blessures mineures ou modérées.
Notice: A notice indicates information that, if not acted on, could result in damage to a system, hardware device, program, or data, but does not present a health or safety hazard.
Note: A note provides important information about the operation of an ftServer system or related equipment or software.

Typographical Conventions

This manual uses the following typographical conventions.

  • Italics introduces or defines new terms. For example:

The master disk is the name of the member disk from which the module was booted.

  • Boldface emphasizes words in text. For example:

Every module must have a copy of the module_start_up.cm file.

  • Monospace represents text that would appear on your terminal's screen (such as commands, subroutines, code fragments, and names of files and directories). For example:
change_current_dir (master_disk)>system>doc 

  • Monospace italic represents terms that are to be replaced by literal values. In the following example, the user must replace the monospace-italic term with a literal value.
list_users -module module_name 

  • Monospace bold represents user input in examples and figures that contain both user input and system output (which appears in monospace). For example:
display_access_list system_default 

%dev#m1>system>acl>system_default

w  *.*

Getting Help

If you have a technical question about ftServer system hardware or software, try these online resources first:

  • Online documentation at the StrataDOC Web site. Stratus provides complimentary access to StrataDOC, an online-documentation service that enables you to view, search, download, and print customer documentation. You can access StrataDOC at the following Web site:

http://stratadoc.stratus.com

  • Online support from Stratus Customer Service. You can find the latest technical information about an ftServer system in the Stratus Customer Service Portal at the following Web site:

http://www.stratus.com/go/support

The Service Portal provides access to Knowledge Base articles for all Stratus product lines. You can locate articles by performing a simple or advanced keyword search, viewing recent articles or top FAQs, or browsing a product and category.

To log in to the Service Portal, enter your employee user name and password or, if you have not been provided with a login account, click Register Account. When registering a new account, ensure that you specify an email address from a company that has a service agreement with Stratus.

If you cannot resolve your questions with these online self-help resources, and the ftServer system is covered by a service agreement, contact the Stratus Customer Assistance Center (CAC) or your authorized Stratus service representative. To contact the CAC, use the Service Portal to log a support request. Click Customer Support and Add Issue, and then complete the Create Issue form. A member of our Customer Service team will be glad to assist you.

Commenting on This Manual

You can comment on this manual using one of the following methods. When you submit a comment, be sure to provide the manual's name and part number, a description of the problem, and the location in the manual where the affected text appears.

  • From StrataDOC, click the site feedback link at the bottom of any page. In the pop-up window, answer the questions and click Submit.
  • From any email client, send email to comments@stratus.com.
  • From the Stratus Customer Service Portal, log on to your account and create a new issue.

Stratus welcomes any corrections and suggestions for improving this manual.