When something goes wrong you should run server in verbose mode (the
-v flag) to see exactly what is the problem. If you
usually run it from inet daemon start it now standalone to some other
-p port flag) with otherwise the
same parameters as in
It's important to understand that rules in the configuration file
Redirect) are translated from top to bottom, and the
Fail will terminate rule translation.
So, make sure that your
rule is before any general
cern_httpdstandalone; this was fixed in version 2.17beta. If you still see zombies (more than two that don't go away in a few minutes) it is a bug.
This is a hard-coded
inetd limitation on at least
SunOS-4.1.* and NeXT, which limits maximum allowed connections
from a given host to 40 per minute. This can be exceeded by
scripts doing Web-roaming, or documents having masses of small
There is a fix for at least SunOS
inetd (100178-08), and
in Solaris this is fixed. You can also run
standalone (preferably with the
-fork command line
Most importantly, you should stop running
inetd and rather run it standalone. This
is because running from
inetd is inefficient.
Map /* file:/*but 2.15 doesn't have this limitation anymore.