You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Rasmus Lerdorf <ra...@lerdorf.on.ca> on 1999/01/13 00:44:35 UTC

Re: Apache 1.3.4 Problem

Oh man, did we really do that?

In article <77...@nnrp1.dejanews.com>, you say...
> Ok, I think I know what's going on here.  It seems that the configure
> script, with the GNU option enabled, creates a slightly different directory
> tree than previous versions.  Specifically, an "httpd" directory is
> appended onto several of the directories.  E.g. instead of
> "sysconfdir: /usr/local/apache/etc", it's
> "sysconfdir: /usr/local/apache/etc/httpd".  These entries are all
> written to the makefile.  Additionally, the src/apaci file
> has httpd directories added:  e.g. "SERVER_CONFIG_FILE" was
> /etc/httpd.conf; now it's /etc/httpd/httpd.conf.
> 
> In my case, a virgin httpd.conf with a port=8080 was created; that's
> why I couldn't start my server, which is at port=80.
> 
> So it appears that the configure script, even with the "--with-layout=GNU",
> will not be compatible with earlier versions, if you're using the APACI
> process.
> 
> --Kevin
> 
> 
> 
> 
> In article <77...@nnrp1.dejanews.com>,
>   ktyle@my-dejanews.com wrote:
> 
> 
> 
> > I attempted upgrading our web server machine from Apache 1.3.3 to Apache
> > 1.3.4.  The machine is running RH Linux 5.1, Kernel 2.0.36.  I did the
> > following to install--basically the same thing I did when I upgraded from
> > 1.3.2 to 1.3.3, with the exception of the --with-layout=GNU:
> >      ./configure --PREFIX=/usr/local/apache --with--layout=GNU
> >      make;make install;/usr/local/apache/sbin/apachectl start
> >
> > I get a seemingly normal response to the start command, but when
> > I try http'ing to localhost I get transported to www.localhost.com,
> > and if I put in the machine's IP address I get the response that the
> > server is down.  There are no messages of any kind in the logs -- not
> > even a "server reconfigured--resuming normal operation" message; no error
> > message, nothing.  However the httpd's are indeed running.
> >
> > I know 1.3.4 is just out of the box--anyone else have any trouble?  Or
> > is there something obvious I've missed?
> >
> > Thanks,
> >
> > Kevin
> >
> > -----------== Posted via Deja News, The Discussion Network ==----------
> > http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own