You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Brandon Metcalf <br...@rackspace.com> on 2010/02/22 16:26:56 UTC
[users@httpd] httpd children receiving SIGHUP
Hello,
I am trying to understand the circumstances under which the httpd parent will SIGHUP its children. MaxRequestsPerChild is set to zero and we are still seeing the child processes receive a SIGHUP after a certain amount of time or requests. Looking at the server status, thread resources are not being exhausted.
Is there some other limit if reached would cause the parent to SIGHUP a child?
Thanks,
Brandon
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@rackspace.com, and delete the original message.
Your cooperation is appreciated.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] httpd children receiving SIGHUP
Posted by Jeff Trawick <tr...@gmail.com>.
On Mon, Feb 22, 2010 at 10:26 AM, Brandon Metcalf
<br...@rackspace.com> wrote:
> Hello,
>
> I am trying to understand the circumstances under which the httpd parent will SIGHUP its children.
SIGHUP should just be sent on non-graceful restart
what is the httpd version and platform? what is the evidence of
SIGHUP vs. some other signal?
>Â MaxRequestsPerChild is set to zero
SIGHUP is not used for that anyway
> and we are still seeing the child processes receive a SIGHUP after a certain amount of time or requests. >Â Looking at the server status, thread resources are not being exhausted.
>
> Is there some other limit if reached would cause the parent to SIGHUP a child?
no
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org