Apache 1.3.19 and Windows Installer

[Michael Larson]

In recent previous versions of Apache for Windows (1.3.14), one could
install multiple instances of the server (for example, separate installs
for each of "n" ports: 80 in C:\program files\apache group\apache, 8000
in C:\program files\apache group\apacheadmin, 8080 in C:\program
files\apache group\apachewhatever, etc.). The new Windows Installer has
apparently removed this capability. Having installed the first
instance, when I start the installer again, my choices are "Repair" and
"Remove" the current installation, and that's it. No mention of, say,
"Install additional server."

Has anyone wanted to do this, and found a way around this insidious
installer?

(I'm running on WinNT 4.0 Server SP-5, if that makes a difference. I
suspect the same will happen in Win2K, since the Installer is integral
to that OS).

Thanks,

Michael Larson

[William A. Rowe, Jr.]

Just xcopy your install into another directory, edit the httpd.conf, and
use the apache -k install -n servicename [where servicename is _different_
than the other services.]

Better answer.

copy httpd.conf to httpd_2.conf. Edit your conf, changing the name of the
PidFile directive, Ports directive, and log files. Then use

apache -k install -n servicename -f conf/httpd_2.conf

No need to pollute your machine with many complete trees :-)

"Michael Larson" <mla...@csub.edu> wrote in message news:3AE4BF7F...@csub.edu...

[Alan McKay]

> In recent previous versions of Apache for Windows (1.3.14), one could
> install multiple instances of the server (for example, separate installs
> for each of "n" ports: 80 in C:\program files\apache group\apache, 8000
> in C:\program files\apache group\apacheadmin, 8080 in C:\program
> files\apache group\apachewhatever, etc.).

What a horrible thing to do! Why would you want to do this when a single
installation of apache can drive as many ports and domain names as you want.
I think you are far better off learning how to use the httpd.conf file to
do what you want to do.

cheers,
-Alan

[William A. Rowe, Jr.]

"Alan McKay" <amc...@americasm01.nt.com> wrote in message news:9c3tiu$ihm$1...@bmerhc5e.ca.nortel.com...

There are several good examples of why you would _not_ use a single .conf.

One, if you want different security contexts on win32 (run service as user...)
then you need several servers/services running.

Second, if you are going to run both tomcat and jserv, you can't (not in a
single server) so you must use two different ones.

Third, if you want the 'fast server' to handle statics, and run another
process for the dodgie scripts on the backend, again this is a good choice.

So I'm presuming this user has some rather legit reasons for wanting more
than one server, it just doesn't take more than one apache 'installation'
to do this.

[Michael Larson]

I'm embarrased to say that I did not even think of such a simple solution as to do the xcopy. I thank
you and shall try it immediately.

My reason, though not as lofty as those you mention, is fairly simple. I have written a web-based remote
admin (in Perl) for Apache, using a second Apache service to run it. I have found it necessary to have a
second server dedicated to this purpose, as it's features involve stopping, starting, and restarting the
service remotely. Seems fairly obvious in this case that it would be difficult to issue a start command
to a stopped service via the stopped service.

Thanks again for the advice. You have truly made my day!

--Mike