Q. Can you explain the tux web server and its usage against regular apache httpd web server?
A. The TUX web server is kernel web server for Linux system. It is currently limited to serving static web pages and coordinating with kernel-space modules, user-space modules, and regular user-space web server daemons to provide dynamic content. Regular user-space web servers do not need to be altered in any way for TUX to coordinate with them. TUX also has the ability to cache dynamic content. TUX modules (which can be build in kernel space or in user space; user space is recommended) can create "objects" which are stored using the page cache. To respond to a request for dynamic data, a TUX module can send a mix of dynamically-generated data and cached pre-generated objects, taking maximal advantage of TUX's zero-copy architecture.
Tux is configured via procfs entries located at /proc/sys/net/tux/. Under CentOS / RHEL / Suse / Fedora Linux Tux can be configured via /etc/sysconfig/tux file.
WARNING! Having an HTTP daemon within the kernel is dangerous, if possible avoid Tux.See Tux manual for configuration options.
However, I don't recommend using Tux. It can be big security problem - a common bug such as a buffer overflow within TUX could give an attacker superuser control over the machine. I recommend lighttpd for static and dynamic configuration.
- Email FAQ to a friend
- Printable version
- Rss Feed
- Last Updated: 04/30/08
{ 0 comments… add one now }
Tagged as: apache httpd, architecture, attacker, buffer overflow, configuration options, daemon, dynamic configuration, dynamic data, fedora linux, httpd web server, kernel space, maximal advantage, page cache, security problem, space modules, space web, static web, web pages, web servers