From: Joshua Slive Date: Sat, 10 Feb 2001 04:12:00 +0000 (+0000) Subject: ServerType is gone in 2.0. X-Git-Tag: 2.0.10~34 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7a0dfe57ddab6a788cdbc749182257a44fd3e7c8;p=apache ServerType is gone in 2.0. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@88048 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index 9bf147aa04..2d138eff0e 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -2432,55 +2432,6 @@ disabled on a virtualhost-by-virtualhost basis.
-

ServerType directive

- -Syntax: ServerType type
-Default: ServerType standalone
-Context: server config
-Status: core
-Compatibility: Removed in version 2.0.

- -The ServerType directive sets how the server is executed by the system. -Type is one of -

-
inetd -
The server will be run from the system process inetd; the command to start -the server is added to /etc/inetd.conf -
standalone -
The server will run as a daemon process; the command to start the server -is added to the system startup scripts. (/etc/rc.local or -/etc/rc3.d/....) -
- -Inetd is the lesser used of the two options. For each http -connection received, a new copy of the server is started from scratch; -after the connection is complete, this program exits. There is a high price to -pay per connection, but for security reasons, some admins prefer this option. -Inetd mode is no longer recommended and does not always -work properly. Avoid it if at all possible. -

- -Standalone is the most common setting for ServerType since -it is far more efficient. The server is started once, and services all -subsequent connections. If you intend running Apache to serve a busy site, -standalone will probably be your only option.

-


-

SetInputFilter directive