From: Dan Kegel <dank@kegel.com>
To: Ken Brownfield <ken@irridia.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"khttpd-users@lists.alt.org" <khttpd-users@alt.org>
Subject: Re: khttpd newbie problem
Date: Thu, 09 May 2002 09:13:12 -0700 [thread overview]
Message-ID: <3CDAA018.F00E8015@kegel.com> (raw)
In-Reply-To: <3CD402D2.E3A94CA2@kegel.com> <20020505005439.GA12430@krispykreme> <3CD4C93D.E543B188@kegel.com> <20020508222119.A12672@asooo.flowerfire.com> <3CDA0876.218285C7@kegel.com> <20020509003155.B12672@asooo.flowerfire.com>
Ken Brownfield wrote:
> Hmm. I've had it running *hard* for two years, never seen a single oops
> or glitch of any sort, kernels 2.4.0-test1 through 2.4.18. O(1),
> preempt, low-latency all on at various times.
Try cycling it up and down in a loop. That's what triggers the bug
my recent patch fixed. (Actually, just starting it once triggers it,
depending on a race condition between the management thread and the
worker threads.)
> | Yukky. Makes me want to go work with user-mode web servers instead.
>
> Yeah, good luck tracking down X15.
I have a copy, actually. It uses Linux's rtsig scheme.
Can't use it, though, as its license prohibits commercial use.
I am tempted to add rtsig support to thttpd, though.
- Dan
next prev parent reply other threads:[~2002-05-09 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 15:48 khttpd newbie problem Dan Kegel
2002-05-05 0:54 ` Anton Blanchard
2002-05-05 5:55 ` Dan Kegel
2002-05-05 11:04 ` Anton Blanchard
2002-05-09 3:21 ` Ken Brownfield
2002-05-09 5:26 ` Dan Kegel
2002-05-09 5:31 ` Ken Brownfield
2002-05-09 16:13 ` Dan Kegel [this message]
2002-05-09 5:46 ` Anton Blanchard
[not found] <200205041600.g44G0J708618@pc3-camc5-0-cust13.cam.cable.ntl.com>
2002-05-04 17:15 ` Dan Kegel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CDAA018.F00E8015@kegel.com \
--to=dank@kegel.com \
--cc=ken@irridia.com \
--cc=khttpd-users@alt.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox