CC'd to David.

David Greenman was going to backport a fix, but I stalled him because
of backwards compatbility.  Since I haven't had the time to implement
the "osendfile" compat syscall, I'd like to know if he'll be MFC'ing the
fix or if I should do it?


* The Hermit Hacker <[EMAIL PROTECTED]> [020521 09:18] wrote:
> I'm looking at getting a threaded Apache working under FreeBSD-STABLE (as
> of this past weekend) ... if I start up the server and connect with a
> browser, it doesn't send anything back, *except* if I kill the apache
> server right after the connection ...
> I've checked with the Apache folk, and someone pointed me to the STATUS
> file, where I found:
> ============
>     * Generate a good bug report to send to the FreeBSD hackers that details
>       the problems we have seen with threads and system calls (specifically
>       sendfile data is corrupted).  From our analysis so far, we don't think
>       that this is an APR issue, but rather a FreeBSD kernel issue.  Our
>       current solution is to just disable threads across the board on
>       FreeBSD.
>       MsgID: <[EMAIL PROTECTED]>
>         Status: Fixed in -CURRENT.  MFC in about a week.  Continuing
>                 testing with threads on FreeBSD.
>                 FreeBSD PR kern/32684:
> ==============
> Reading the PR, alfred put a fix in place shortly after (~mid December of
> 2001), but I'm wondering if anyone knows whether this was migrated back
> down to -STABLE, and, if not, what would be involved to have that done?
> Is it a fix that *can* be MFCd?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to