Loading docs/manual/misc/FAQ.html +46 −13 Original line number Diff line number Diff line Loading @@ -8,7 +8,7 @@ <!--#include virtual="header.html" --> <H1>Apache Server Frequently Asked Questions</H1> <P> $Revision: 1.39 $ ($Date: 1997/04/22 11:20:04 $) $Revision: 1.40 $ ($Date: 1997/04/22 12:05:52 $) </P> <P> The latest version of this FAQ is always available from the main Loading Loading @@ -148,6 +148,9 @@ <LI><A HREF="#linuxiovec">Why do I get complaints about redefinition of `struct iovec' when compiling under Linux?</A> </LI> <LI><A HREF="#wheres-the-dump">The errorlog says Apache dumped core, but where's the dump file?</A> </LI> </OL> </LI> </UL> Loading Loading @@ -1040,6 +1043,36 @@ </UL> </P> <HR> </LI> <LI><A NAME="wheres-the-dump"> <STRONG>The errorlog says Apache dumped core, but where's the dump file?</STRONG> </A> <P> In Apache version 1.2 (beginning with 1.2b8), the error log message about dumped core includes the directory where the dump file should be located. However, some operating systems regard the dumping of core by processes with superuser authority as a potential security issue, and short-circuit the dump code, leaving no file. Since most Web servers listen on port 80 (a privileged port), they need to run with superuser authority, and so this short-circuit will apply to them. </P> <P> Dealing with this is extremely operating system-specific, and may require rebuilding your system kernel. Consult your operating system documentation or vendor for more information about whether your system does this and how to bypass it. If there <EM>is</EM> a documented way of bypassing it, it is recommended that you bypass it only for the <SAMP>httpd</SAMP> server process if possible. </P> <P> The canonical location for Apache's core-dump files is the <A HREF="../mod/core.html#serverrot" >ServerRoot</A> directory. </P> <HR> <!-- Don't forget to add HR tags at the end of each list item.. --> </LI> </OL> Loading Loading
docs/manual/misc/FAQ.html +46 −13 Original line number Diff line number Diff line Loading @@ -8,7 +8,7 @@ <!--#include virtual="header.html" --> <H1>Apache Server Frequently Asked Questions</H1> <P> $Revision: 1.39 $ ($Date: 1997/04/22 11:20:04 $) $Revision: 1.40 $ ($Date: 1997/04/22 12:05:52 $) </P> <P> The latest version of this FAQ is always available from the main Loading Loading @@ -148,6 +148,9 @@ <LI><A HREF="#linuxiovec">Why do I get complaints about redefinition of `struct iovec' when compiling under Linux?</A> </LI> <LI><A HREF="#wheres-the-dump">The errorlog says Apache dumped core, but where's the dump file?</A> </LI> </OL> </LI> </UL> Loading Loading @@ -1040,6 +1043,36 @@ </UL> </P> <HR> </LI> <LI><A NAME="wheres-the-dump"> <STRONG>The errorlog says Apache dumped core, but where's the dump file?</STRONG> </A> <P> In Apache version 1.2 (beginning with 1.2b8), the error log message about dumped core includes the directory where the dump file should be located. However, some operating systems regard the dumping of core by processes with superuser authority as a potential security issue, and short-circuit the dump code, leaving no file. Since most Web servers listen on port 80 (a privileged port), they need to run with superuser authority, and so this short-circuit will apply to them. </P> <P> Dealing with this is extremely operating system-specific, and may require rebuilding your system kernel. Consult your operating system documentation or vendor for more information about whether your system does this and how to bypass it. If there <EM>is</EM> a documented way of bypassing it, it is recommended that you bypass it only for the <SAMP>httpd</SAMP> server process if possible. </P> <P> The canonical location for Apache's core-dump files is the <A HREF="../mod/core.html#serverrot" >ServerRoot</A> directory. </P> <HR> <!-- Don't forget to add HR tags at the end of each list item.. --> </LI> </OL> Loading