iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)

Configuration Directives
iTP Secure WebServer System Administrator’s Guide—522659-001
A-37
Pidfile
serverclassname
a valid NonStop TS/MP server class name. If you do not specify a server-class
name, the server class is presumed to have the same name as the file, minus the
extension. For example, the file logon.ab_demo would be referred to a server class
called logon in the PATHMON environment indicated by the PATHMON name.
Examples
Here are some examples of the PathwayMimeMap directive. The first example
specifies a server-class name, the second specifies a PATHMON name, and the third
specifies both:
PathwayMimeMap tcltcl-server
PathwayMimeMap userapp/G/UA
PathwayMimeMap userapp2/G/UA:ua2-server
The next set of examples shows the relationship between a PathwayMimeMap
directive and the corresponding MimeType directive. The MimeType directive must
precede the PathwayMimeMap directive but does not have to appear directly before it
as shown. The two MimeType directives below indicate that files with the extension
cgi and ab_demo have the MIME type
application x/httpd-guardian. The
corresponding PathwayMimeMap directives indicate that files with the extension cgi
are processed by the generic-cgi server class, and files with the extension ab_demo are
processed by a server class under control of the PATHMON process /G/ZAB or $ZAB.
MimeType application x/httpd-guardian cgi
PathwayMimeMap cgi generic-cgi
MimeType application/x-httpd-guardian ab_demo
PathwayMimeMap ab_demo /G/ZAB
Pidfile
Syntax
PidFile filename
Description
You set the PidFile directive to the file in which the server is to record the server
process ID.
The PidFile directive is optional. Only one PidFile directive is allowed in the
configuration file.
Default
None. If you do not set the PidFile directive, no process ID file is written.
Example
PidFile /usr/tandem/webserver/httpd.pid