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
port (with -p
port flag) with otherwise the
same parameters as in /etc/inetd.conf.
:-(
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
inlined images.
There is a fix for at least SunOS inetd
(100178-08), and
in Solaris this is fixed. You can also run httpd
standalone (preferably with the -fork
command line
option).
Most importantly, you should stop running
httpd
from inetd
and rather run it standalone. This is because
running from inetd
is inefficient.
Map /* file:/*but for 2.15 doesn't have this limitation anymore.
httpd,
e.g.
httpd /home/me/MyGloriousWeb