>> I tried making Apache inetd and changed the inetd.conf file to indicate
>> this.  Services has also been modified to listen to port 80 for httpd.
>
>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 :)
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?
sorry, pat, there seems to be a much better solution to run it
automatically..:)
thanks,
  - a