Communicator e3000 MPE/iX Release 6.5 Express 2 (Software Release C.65.02) (30216-90322)

Chapter 3 29
Technical Articles
Apache 1.3.9 for MPE/iX
installation, you need to create your own copies of these. The httpd.conf.sample file was
derived from the httpd.conf.default file with modifications for Apache on MPE/iX.
Make sure you are logged on as MGR.APACHE before beginning configuration,
:HELLO MGR.APACHE
:xeq sh.hpbin.sys -L
shell/iX>cd /APACHE/PUB/conf
shell/iX>cp httpd.conf.sample httpd.conf
shell/iX>cp mime.types.default mime.types
shell/iX>cp magic.default magic
The access.conf.default file and the srm.conf.default file need not be copied. These files
were used in earlier versions of Apache but their content is now included in the httpd.conf
file. However, if these files exist, Apache will read and process them after processing the
conf/httpd.conf file.
httpd.conf
Edit the httpd.conf file for your own server. You may also wish to change default values.
For information about configuration directives, visit the online Apache documentation at
http://www.apache.org/docs. Httpd.conf is a bytestream file. If you have Samba installed,
you can edit httpd.conf on your PC.
Modify the following httpd.conf directives by replacing "yourserver.com" with your own
server name:
• ServerAdmin [e-mail]
• ServerName yourserver.com
JHTTPD Job Stream File
The startup job stream file, JHTTPD, is provided as a sample file to prevent overwriting
JHTTPD on an existing installation. For new installations, copy the sample file then
change the timezone variable, TZ, to your own timezone. Note that the file mask is now set
in this file. JHTTPD is an MPE, fixed-record filetype which can be edited with any MPE
text editor.
shell/iX>cd /APACHE/PUB
shell/iX>cp JHTTPD.sample JHTTPD
shell/iX>cat JHTTPD
!job jhttpd,www.apache,pub;outclass=,2
!setvar TZ 'PST8PDT'
!xeq sh.hpbin.sys “-c ‘umask 007;./HTTPD -f /APACHE/PUB/conf/httpd.conf‘”
!eoj
Updating from Earlier Versions
If you are updating from earlier versions of Apache, rename or remove the existing log files
after stopping Apache. This way, Apache can create fresh log files with the correct
ownership and permissions. Startup errors will also be easier to detect. Make sure to stop
Apache before renaming or trying to remove these files. Apache will continue to hold log
files open and write to them while it is running.