httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Murcko <ch...@topsail.org>
Subject Re: [STATUS] Sun Apr 13 19:08:09 PDT 1997
Date Mon, 14 Apr 1997 04:23:02 GMT
Dean Gaudet wrote:
> 
> 1.2b9 status as of Sun Apr 13 19:08:09 PDT 1997
> 
>   * Committed since 1.2b8:
> 
>     * the new FAQ
>     * #define memmove for SUNOS4
>     * ftp proxy improvements
PR #279
>     * proxy uses multiple A records if needed
PR #304
>     * mod_example
>     * mod_rewrite 3.0.3
>     * more signed/unsigned port cleanups
>     * allow HARD_SERVER_LIMIT to be changed in Configuration
>     * UnixWare compile/install instructions
>     * PR#369: set SHELL in Configure to deal with ULTRIX /bin/sh5
>     * PR#380: tweak to modules/Makefile generation
>     * PR#293: redirect did not preserve query strings
> 
> Agenda for 1.2b9-dev
> ====================
> 
> Patches available:
> 
>   * Dean's [PATCH] yet another mod_negotiation sub_req copy thing
>     <Pine.LNX.3.95dg3.970412021814.19336J-100000@twinlark.arctic.org>
> 
>   * Ralf's [PATCH] FreeBSD and SIGPIPE: perhaps solved?
>     <199704121143.NAA13911@en1.engelschall.com>
> 
> 1.2 Showstoppers with no patches yet:
> 
>   * redirect of index file causes SEGV [Marc]
>         Status: have a way to stop the core dump, but that doesn't make
>         it work properly.
>         See also: <Pine.BSF.3.91.970210204402.12197B-100000@localhost.imdb.com>
> 
>   * SEGV under FreeBSD with lingering_close [and proxy?]
>         <3331034D.167EB0E7@topsail.org>
>         Chuck says: Roy's latest timeout patches have stopped the lingering
>         close notifications, but the core dumps continue. The dumped image
>         is so trashed that it can't be backtraced. I believe the reason we
>         haven't seen more reports is that FreeBSD and perhaps Linux are
>         disabling core dumps by default as a security measure.
> 
Randy, are you still seeing these? I've gotten no core dumps in about a
week of heavy testing since all of Roy's patches went in, and I fixed
some other things in the proxy.
> 
> UnixWare:
> 
>     Chuck thinks all of these are solved using the method presented by
>     Joe D.  Chuck will include correspondence from folks who have successfully
>     run Apache on all known versions of UnixWare.
> 
>     * SIGTERM to parent on UnixWare kills it but leaves children as
>         zombies, requiring reboot.  SIGHUP reloads it fine when it's
>         running. (no PR#, 1.2b6, 21/2/1997, <talbion@xl.ca>)
> 
>     * Randy says "seems that the processes on a Unixware machine are
>         eventually all dying off. Mind you, I have not seen this, but
>         that is what is being reported.  Sounds like perhaps the server is not
>         respawning new children after MaxRequestsPerChild has been reached."
> 
See the UnixWare build docs and patch descriptions I added. It looks
like all these are covered if you patch the OS correctly.
-- 
chuck
Chuck Murcko
The Topsail Group, West Chester PA USA
chuck@topsail.org

Mime
View raw message