> > >eeeewwwwww.  Don't run a web server w/ inetd.  It's _much_ less efficient.
> > >Apache (and NCSA beginning with 1.4 or 1.5) both prefork several copies of
> > >themselves running at once to handle hits at maximum efficiency.  The use
> > >of inetd to control it bogs things way down (inetd has to fork for every
> > >web request, http server starts, serves, quits... very ugly).
> > >
> > 
> > heh :)
> > inetd is for us lazy folks who don't type httpd upon root shell and get two
> > hits/month, and probably from ourselves :)
> 
> :-)

Believe it or not, it still slows down the responsiveness of the server, 
even if you are the only one using it ;-)

> > come to think of it, you are right, and i (being fairly new to unix)
> > thought the multiple httpd process idea would work, anyway, and i wasn't
> > really thinking in terms of efficiency. so what should be done to get it
> > run automatically as root in a nice way? use crontab, or you know of other
> > ways?
> 
> best way is to put it... (switching from MkLinux to NetBSD mode) either
> (tentatively) at the end of netstart, perhaps... or preferrably in
> rc.local (both in /etc). 

ewwww...don't put it in /etc/netstart.  That file is _only_ for 
configuring network interfaces, not network daemons.  Add a little 
something like the following to /etc/rc.local:

# Set up httpd
if [ -f /usr/local/httpd/bin/httpd ] ; then
        echo -n ' httpd'
        /usr/local/httpd/bin/httpd -d /usr/local/httpd
fi

Of course, make sure the path reflects the actual state of things on your 
system.

I hope this helps.

Later.

-- 
Colin Wood                                      ender@is.rice.edu
Consultant                                        Rice University
Information Technology Services                       Houston, TX