From: Dan Kegel <dank@kegel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: khttpd newbie problem
Date: Sat, 04 May 2002 08:48:34 -0700 [thread overview]
Message-ID: <3CD402D2.E3A94CA2@kegel.com> (raw)
I'm having an oops with khttpd on an embedded 2.4.17 ppc405
system, so I thought I'd try it out on my pc. But I can't
get khttpd to serve any requests.
I built khttpd into the kernel with vanilla 2.4.17smp on
Intel on Red Hat 7.2, then turned it on as follows:
echo /home/dank/stress > /proc/sys/net/khttpd/documentroot
echo 80 > /proc/sys/net/khttpd/serverport
echo 8000 > /proc/sys/net/khttpd/maxconnect
echo 1 > /proc/sys/net/khttpd/start
I also made sure there was an index.html in /home/dank/stress,
turned off the firewall, did /etc/init.c/ipchains restart,
and made sure netstat reported port 80 as listening.
But... when I try to fetch http://localhost/index.html,
it just sits there. Likewise, when I telnet to port 80,
even from a different machine, it just accepts bytes forever;
no matter what I type, it just echoes the bytes right back at me.
If I do
echo 1 > /proc/sys/net/khttpd/stop
port 80 stops listening, and any open connections are closed.
I must be doing something silly... surely khttpd works?
Is it because I'm running SMP, perhaps?
- Dan
next reply other threads:[~2002-05-04 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 15:48 Dan Kegel [this message]
2002-05-05 0:54 ` khttpd newbie problem 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
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=3CD402D2.E3A94CA2@kegel.com \
--to=dank@kegel.com \
--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