httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: New Installer for Win32
Date Tue, 30 Jan 2001 20:37:04 GMT
Bill, Scott, thanks both for your research.

I think the problem is in preexisting 'Apache' services.  The new candidate,

does things a bit differently.

1. Stops the service in any mode (install/remove/repair)

2. Removes the service when when uninstalling.

files get added or deleted, confs are rewritten

3. Removes a preexisting Apache service only when installing

4. Installs its service only when installing.

5. Restarts the service (in any mode but uninstalling).

Really tangled, I think this fixes things.

I'm 50/50 for restricting steps 3,4,5 to Windows NT only.

As for dangling .conf files... I'll look at that right away.  Note that the
installer gladly overwrites any pre-existing .default.conf files, since we
are only interested in the current installation.  But we do not overwrite
existing httpd.conf files.  Same goes with dangling .log files.


----- Original Message ----- 
From: "Bill Stoddard" <>
To: <>
Sent: Tuesday, January 30, 2001 2:00 PM
Subject: Re: New Installer for Win32

> > > > and everything appears to go well up until the point the install
> automagically
> > > > starts apache. The child process is started then dies. The parent then
> goes
> > > > into a loop restarting the child each time it dies. Nothing in the error
> log.
> > >
> > > Still seeing this in rc2.
> >
> > But not the double-slashed ServerRoot, I hope?
> >
> DocumentRoot & ServerRoot and Directorys look good in rc2.
> The problem appears to be that the installation tries to start apache in a
> console. I close the console and the parent/child loop goes away (and the
> service is already started).
> Bill

View raw message