httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matus UHLAR - fantomas <>
Subject Re: [users@httpd] Incomplete file downloads if Apache HTTPD is killed
Date Mon, 09 May 2011 13:44:19 GMT
> >< if a server is killed (SIGKILL) during a "large" static file transfer, then
> >> the client is not notified by his browser that file has not been completely
> >> downloaded. On Win it just says it is not a valid Win32 application or
> >> corrupted or sth.
> >> Now I know this is not a general problem and a graceful restart is the way
> >> to go around this, but if I do an upgrade then proper restart is required,
> >> or at least I think I remember I had problems with graceful restart in such
> >> situations.
> >>
> >
> > Sending a SIGKILL is an unfriendly way to end a process -- it causes the
> > kernel to immediately terminate the process, without giving the process any
> > chance to clean up.  SIGKILL is thus not one of the signals handled
> > specially by Apache HTTP Server.  For a list of the signals that are handled
> > specially, see

On 20.04.11 20:19, Bostjan Skufca wrote:
> Sending SIGKILL was just a way to simulate apachectl stop, which sends
> SIGTERM and then if after 10s some children still did not exit, parent sends
> SIGKILL to them.

So that was bad way to simulate "apachectl stop" just because of the above.
I think with 2.2 it even is not true, because apache2 has own way to
configure shutdown timeouts, the GracefulShutdownTimeout directive.

While talking about killed server and knowing that the file was
transferred - It's often impossible to know. The chunked encoding or the
Content-Length header are needed to know if the whole file was transfered.

Matus UHLAR - fantomas, ;
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
WinError #99999: Out of error messages.

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message