Apache 1.3.12 setup

Okay, you've got it built, now do a "make install" as root. The default from configure will be to install into /usr/local/apache. If that's not acceptable you'll have to re-run configure and specify a new installation directory, like "./configure --prefix=/path-to/apache" and them re-make everything.

When it's been installed you need to setup Apache's configuration. The file to modify is /path-to/apache/conf/httpd.conf. Make sure that you properly set ServerName on Solaris. If "hostname" returns the short name for your system, you'll have to set ServerName to be the FQDN of the system.

When the conf file looks good, check it by executing "/path-to/apache/bin/httpdctl configtest" to check the config file for errors. If everything looks okay, start the server with "/path-to/apache/bin/httpdctl start".

I have run make install before, and I made a user called web, and installed it in ~web/apache_1.3.12.  The httpd.conf looks ok.

There is no httpdctl file, but there is an apachectl file which the readme files said to run.  when I do 'apachectl configtest', it returns 'Syntax OK'.  When I do 'apachectl start', it returns 'apachectl start: httpd started'.  However, ps -A still doesn't show any sign of a web server running..

What configure options did you use and what dir does ~web translate to?

~web is /export/home/web and while in /export/home/web/apache_1.3.12/bin, I ran the command './apachectl start'.

Here are some of the settings in httpd.conf that I changed (or looked at long enough that it made an impact on me):
ServerType standalone
ServerRoot /export/home/web/apache_1.3.12
Port 80
User nobody
Group #-1
ServerAdmin root@xxx.xxx.uci.edu
ServerName xxx.xxx.uci.edu
DocumentRoot /export/home/web/apache_1.3.12/htdocs
HostnameLookups On


On a side note, there was this comment with Port 80 --
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.

I tried changing User to root and it complained about that, telling me that I needed to set some flag and recompile it..

Uh, my mistake on the httpdctl, they've changed it yet again (back to apachectl). I hadn't yet fetched the 1.3.12 and was looking at the prior version.

Gimme a couple of hours & I'll set 1.3.12 up and be able to tell you exactly how to fix it.

I still need to know what your configure options were. If you're not sure what you used, they are recorded in "config.status" at the top level of the source tree.

Here are the contents of config.status

#!/bin/sh
##
##  config.status -- APACI auto-generated configuration restore script
##
##  Use this shell script to re-run the APACI configure script for
##  restoring your configuration. Additional parameters can be supplied.
##

../configure \
"--with-layout=Apache" \
"--prefix=/export/home/web/apache_1.3.12" \
"$@"

Maybe I should just try a different version of apache =)

Naa, it'll work... Just take me a bit to get one built and check the differences between 1.3.12 and the 1.3.9/1.3.11 versions that I've got running.

hmm.. I just tried apache 1.3.11 and it worked straight out.. no problems whatsoever..

If you feel like going on with the 1.3.12 thing though, feel free to and I'll keep up to speed with you on that..

If not, go ahead and post an answer to get your points since your answer is technically correct =)

I'll wait until I get the 1.3.12 up and then post the correct answer for that. I had intended to do so this week anyway. So stay tuned.

Well, it worked.. go figure =)

Did you have a chance to look at what "enable-module=most" and "enable-shared=max" does for you?

The resultant server has a lot more features and it's much easier to add other (not distribution) modules. The memory foot print for the child servers that actually serve pages is quite a bit less as a lot of what they migh need is shared between all children.