On Mon, Jan 24, 2011 at 8:17 PM, Andrew Punch <andrew.punch@xxxxxxxxxxxxxxxx> wrote: > Hi, > > During the week I hit the situation described in 41743. A child process > is connected to a client using a keepalive connection. A graceful > restart (SIGUSR1) is issued. If the MaxKeepAliveRequests is high and the > client is chatty the child process will not exit until the client > disconnects. > > This means that my module in the child process still has the old > configuration and old data file loaded in memory. I expected that the > child process would close the keepalive connection - preferably by > issuing a "connection: close" header in the next response. > > This problem occurs on RHEL5 with Redhat's Apache 2.2.3 and > httpd.apache.org's Apache 2.2.17 > > Is this behaviour deliberate or is it a bug? Looks like a difference between prefork and worker. -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- 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@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|