marc 97/07/02 11:07:18
Modified: htdocs/manual vhosts-in-depth.html
htdocs/manual/misc descriptors.html
Log:
Fix bogus HTML.
Revision Changes Path
1.10 +8 -4 apache/htdocs/manual/vhosts-in-depth.html
Index: vhosts-in-depth.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/vhosts-in-depth.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -C3 -r1.9 -r1.10
*** vhosts-in-depth.html 1997/06/04 11:07:52 1.9
--- vhosts-in-depth.html 1997/07/02 18:07:16 1.10
***************
*** 357,379 ****
<li>Place all main_server definitions before any VirtualHost definitions.
(This is to aid the readability of the configuration -- the post-config
merging process makes it non-obvious that definitions mixed in around
! virtualhosts might affect all virtualhosts.)</p>
<li>Arrange your VirtualHosts such
that all name-based virtual hosts come first, followed by IP-based
! virtual hosts, followed by any <SAMP>_default_</SAMP> virtual host</p>
<li>Avoid <code>ServerPaths</code> which are prefixes of other
<code>ServerPaths</code>. If you cannot avoid this then you have to
ensure that the longer (more specific) prefix vhost appears earlier in
the configuration file than the shorter (less specific) prefix
(<EM>i.e.</EM>, "ServerPath /abc" should appear after
! "ServerPath /abcdef"). </p>
<li>Do not use <i>port-based</i> vhosts in the same server as
name-based vhosts. A loose definition for port-based is a vhost which
is determined by the port on the server (<em>i.e.</em> one server with
! ports 8000, 8080, and 80 all of which have different configurations).</p>
</ul>
--- 357,383 ----
<li>Place all main_server definitions before any VirtualHost definitions.
(This is to aid the readability of the configuration -- the post-config
merging process makes it non-obvious that definitions mixed in around
! virtualhosts might affect all virtualhosts.)
! <p>
<li>Arrange your VirtualHosts such
that all name-based virtual hosts come first, followed by IP-based
! virtual hosts, followed by any <SAMP>_default_</SAMP> virtual host
! <p>
<li>Avoid <code>ServerPaths</code> which are prefixes of other
<code>ServerPaths</code>. If you cannot avoid this then you have to
ensure that the longer (more specific) prefix vhost appears earlier in
the configuration file than the shorter (less specific) prefix
(<EM>i.e.</EM>, "ServerPath /abc" should appear after
! "ServerPath /abcdef").
! <p>
<li>Do not use <i>port-based</i> vhosts in the same server as
name-based vhosts. A loose definition for port-based is a vhost which
is determined by the port on the server (<em>i.e.</em> one server with
! ports 8000, 8080, and 80 all of which have different configurations).
! <p>
</ul>
1.3 +6 -6 apache/htdocs/manual/misc/descriptors.html
Index: descriptors.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/misc/descriptors.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** descriptors.html 1997/07/02 03:23:06 1.2
--- descriptors.html 1997/07/02 18:07:17 1.3
***************
*** 73,85 ****
will run into trouble if more than approximately 240 Listen
directives are used. This may be cured by rebuilding your kernel
with a higher FD_SETSIZE.
! </p>
<dt> <b>FreeBSD 2.2, BSDI 2.1+</b>
<dd> Similar to the BSDI 2.0 case, you should define
<code>FD_SETSIZE</code> and rebuild. But the extra
Listen limitation doesn't exist.
! </p>
<dt> <b>Linux</b>
<dd> By default Linux has a kernel maximum of 256 open descriptors
--- 73,85 ----
will run into trouble if more than approximately 240 Listen
directives are used. This may be cured by rebuilding your kernel
with a higher FD_SETSIZE.
! <p>
<dt> <b>FreeBSD 2.2, BSDI 2.1+</b>
<dd> Similar to the BSDI 2.0 case, you should define
<code>FD_SETSIZE</code> and rebuild. But the extra
Listen limitation doesn't exist.
! <p>
<dt> <b>Linux</b>
<dd> By default Linux has a kernel maximum of 256 open descriptors
***************
*** 95,101 ****
256. As of this writing the patches available for increasing
the number of descriptors do not take this into account. On a
dedicated webserver you probably won't run into trouble.
! </p>
<dt> <b>Solaris through 2.5.1</b>
<dd> Solaris has a kernel hard limit of 1024 (may be lower in earlier
--- 95,101 ----
256. As of this writing the patches available for increasing
the number of descriptors do not take this into account. On a
dedicated webserver you probably won't run into trouble.
! <p>
<dt> <b>Solaris through 2.5.1</b>
<dd> Solaris has a kernel hard limit of 1024 (may be lower in earlier
***************
*** 107,124 ****
build Apache with <code>-DHIGH_SLACK_LINE=256</code> added to
<code>EXTRA_CFLAGS</code>. You will be limited to approximately
240 error logs if you do this.
! </p>
<dt> <b>AIX version ??</b>
<dd> AIX appears to have a hard limit of 128 descriptors. End of
story.
! </p>
<dt> <b>Others</b>
<dd> If you have details on another operating system, please submit
it through our <a href="http://www.apache.org/bug_report.html";>Bug
Report Page</a>.
! </p>
</dl>
--- 107,124 ----
build Apache with <code>-DHIGH_SLACK_LINE=256</code> added to
<code>EXTRA_CFLAGS</code>. You will be limited to approximately
240 error logs if you do this.
! <p>
<dt> <b>AIX version ??</b>
<dd> AIX appears to have a hard limit of 128 descriptors. End of
story.
! <p>
<dt> <b>Others</b>
<dd> If you have details on another operating system, please submit
it through our <a href="http://www.apache.org/bug_report.html";>Bug
Report Page</a>.
! <p>
</dl>
