Running Tux with no secondary server?

[William M. Shubert]

I was considering Tux for a server of mine, but the configuration I was
planning isn't one of the two recommended in the docs, so I thought I'd
check here and make sure it wouldn't cause errors.

Basically, I want to run Tux with no secondary server. Any requests that
Tux can't answer should get a static error page.

My reason is that the server is very busy with a large application. It
has a large number of files (over a million) which it needs to touch
often, and which get downloaded to web clients fairly often as well.
Right now it runs Apache, which takes up a decent chunk of memory that
I'd rather use for the "main" application. Tux seems to use a lot less
memory - especially on a per connection basis.

Since I have no dynamic content at all coming off of this system, is
this possible with Tux? I see tux has a /proc entry for the port of the
secondary web server, should I do anything special there to tell tux
"don't bother," or would it be OK to just leave that value at some port
that nobody is listening on?

Thanks. If Tux can't do this I guess I'll look into other web servers
that are lighter than apache, but seems that Tux is the lightest of them
all, and comes on RHEL by default, so it would be my first choice.
        Bill Shubert (wms at igoweb.org)