patch-2.4.20 linux-2.4.20/net/khttpd/README
Next file: linux-2.4.20/net/khttpd/main.c
Previous file: linux-2.4.20/net/irda/qos.c
Back to the patch index
Back to the overall index
- Lines: 109
- Date:
Thu Nov 28 15:53:16 2002
- Orig file:
linux-2.4.19/net/khttpd/README
- Orig date:
Thu Nov 16 14:07:53 2000
diff -urN linux-2.4.19/net/khttpd/README linux-2.4.20/net/khttpd/README
@@ -14,14 +14,15 @@
other webservers in that it runs from within the Linux-kernel as a module
(device-driver).
- kHTTPd handles only static (file based) web-pages, and passes all requests
- for non-static information to a regular userspace-webserver such as Apache or
- Zeus. The userspace-daemon doesn't have to be altered in any way.
+ kHTTPd handles only static (file based) web-pages, and passes all requests
+ for non-static information to a regular userspace-webserver such as Apache
+ or Zeus. The userspace-daemon doesn't have to be altered in any way.
Static web-pages are not a very complex thing to serve, but these are very
important nevertheless, since virtually all images are static, and a large
portion of the html-pages are static also. A "regular" webserver has little
- added value for static pages, it is simply a "copy file to network"-operation.
+ added value for static pages, it is simply a "copy file to network"
+ operation.
This can be done very efficiently from within the Linux-kernel, for example
the nfs (network file system) daemon performs a similar task and also runs
in the kernel.
@@ -44,6 +45,7 @@
echo 1 > /proc/sys/net/khttpd/stop
echo 1 > /proc/sys/net/khttpd/unload
+ sleep 2
rmmod khttpd
@@ -71,7 +73,7 @@
Before you can start using kHTTPd, you have to configure it. This
is done through the /proc filesystem, and can thus be done from inside
- a script. Most parameters can only be set when kHTTPd is not active.
+ a script. Most parameters can only be set when kHTTPd is stopped.
The following things need configuration:
@@ -117,26 +119,31 @@
Port 8080
+ Starting kHTTPd
+ ===============
+ Once you have set up the configuration, start kHTTPD by running
+ echo 1 > /proc/sys/net/khttpd/start
+ It may take a jiffie or two to start.
-
Stopping kHTTPd
===============
- In order to change the configuration, you should stop kHTTPd by typing
+ To stop kHTTPd, do
echo 1 > /proc/sys/net/khttpd/stop
- on a command-prompt.
+ It should stop in a jiffy or two.
- If you want to unload the module, you should type
+ Unloading kHTTPd
+ ===============
+ To unload the module, do
+ echo 1 > /proc/sys/net/khttpd/stop
echo 1 > /proc/sys/net/khttpd/unload
- after stopping kHTTPd first.
+ #killall -HUP khttpd
+ sleep 2
+ rmmod khttpd
- If this doesn't work fast enough for you (the commands above can wait for
+ If this doesn't work fast enough for you (unloading can wait for
a remote connection to close down), you can send the daemons a "HUP"
signal after you told them to stop. This will cause the daemon-threads to
stop immediately.
-
- Note that the daemons will restart immediately if they are not told to
- stop.
-
4. Permissions
@@ -212,7 +219,21 @@
maxconnect 1000 Maximum number of concurrent
connections
-6. More information
+6. Known Issues
+ kHTTPd is *not* currently compatible with tmpfs. Trying to serve
+ files stored on a tmpfs partition is known to cause kernel oopses
+ as of 2.4.18. This is due to the same problem that prevents sendfile()
+ from being usable with tmpfs. A tmpfs patch is floating around that seems
+ to fix this, but has not been released as of 27 May 2002.
+ kHTTPD does work fine with ramfs, though.
+
+ There is debate about whether to remove kHTTPd from the main
+ kernel sources. This will probably happen in the 2.5 kernel series,
+ after which khttpd will still be available as a patch.
+
+ The kHTTPd source code could use a good spring cleaning.
+
+7. More information
-------------------
More information about the architecture of kHTTPd, the mailinglist and
configuration-examples can be found at the kHTTPd homepage:
@@ -221,4 +242,6 @@
Bugreports, patches, etc can be send to the mailinglist
(khttpd-users@zgp.org) or to khttpd@fenrus.demon.nl
+ Mailing list archives are at
+ http://lists.alt.org/mailman/listinfo/khttpd-users
FUNET's LINUX-ADM group, linux-adm@nic.funet.fi
TCL-scripts by Sam Shen (who was at: slshen@lbl.gov)