I just installed apache 2.0, everything works great so I am off to a
good start but i have a few newbie questions. I didn't bother to
verify that my linux install had apache already bundled in the distro
so I compiled apache 2.2 myself. Now I have two httpd directory paths
(/etc/httpd; and /usr/local/apache2). I verified which httpd.conf is
being invoked during start up, (the bundled /etc/httpd versioon) but
the very fact that there are two versions has me confused. The
httpd.conf under the bundled directory has a lot more configuration
info, but the complied version has more modified configuration info.
Should I merge the two httpd.conf files? Could I just upgrade 2.0 with
the newly installed 2.2? Thanks.

On 7 Jul 2006 15:56:37 -0700, dchristensen@novarra.com wrote:
> I just installed apache 2.0, everything works great so I am off to a
> good start but i have a few newbie questions. I didn't bother to
> verify that my linux install had apache already bundled in the distro
> so I compiled apache 2.2 myself. Now I have two httpd directory paths
> (/etc/httpd; and /usr/local/apache2). I verified which httpd.conf is
> being invoked during start up, (the bundled /etc/httpd versioon) but
> the very fact that there are two versions has me confused. The
> httpd.conf under the bundled directory has a lot more configuration
> info, but the complied version has more modified configuration info.
> Should I merge the two httpd.conf files? Could I just upgrade 2.0 with
> the newly installed 2.2? Thanks.

Since you're a newbie... unless you know you need 2.2 for some
particular reason (super-large files, for example), I would say delete
the 2.2 stuff and use the 2.0 that came with your Linux. It "just
works" out-of-the-box, and you can get better support / that way.

It's likely that there are config options for 2.2 that won't work with,
or might break, 2.0 Merging those files would be a Really Bad Idea.

--
* John Oliver http://www.john-oliver.net/ *

On 7 Jul 2006 15:56:37 -0700, dchristensen@novarra.com wrote:
> I just installed apache 2.0, everything works great so I am off to a
> good start but i have a few newbie questions. I didn't bother to
> verify that my linux install had apache already bundled in the distro
> so I compiled apache 2.2 myself. Now I have two httpd directory paths
> (/etc/httpd; and /usr/local/apache2). I verified which httpd.conf is
> being invoked during start up, (the bundled /etc/httpd versioon) but
> the very fact that there are two versions has me confused. The
> httpd.conf under the bundled directory has a lot more configuration
> info, but the complied version has more modified configuration info.
> Should I merge the two httpd.conf files? Could I just upgrade 2.0 with
> the newly installed 2.2? Thanks.

Since you're a newbie... unless you know you need 2.2 for some
particular reason (super-large files, for example), I would say delete
the 2.2 stuff and use the 2.0 that came with your Linux. It "just
works" out-of-the-box, and you can get better support / that way.

It's likely that there are config options for 2.2 that won't work with,
or might break, 2.0 Merging those files would be a Really Bad Idea.

--
* John Oliver http://www.john-oliver.net/ *

On 7 Jul 2006 15:56:37 -0700, dchristensen@novarra.com wrote:
> I just installed apache 2.0, everything works great so I am off to a
> good start but i have a few newbie questions. I didn't bother to
> verify that my linux install had apache already bundled in the distro
> so I compiled apache 2.2 myself. Now I have two httpd directory paths
> (/etc/httpd; and /usr/local/apache2). I verified which httpd.conf is
> being invoked during start up, (the bundled /etc/httpd versioon) but
> the very fact that there are two versions has me confused. The
> httpd.conf under the bundled directory has a lot more configuration
> info, but the complied version has more modified configuration info.
> Should I merge the two httpd.conf files? Could I just upgrade 2.0 with
> the newly installed 2.2? Thanks.

Since you're a newbie... unless you know you need 2.2 for some
particular reason (super-large files, for example), I would say delete
the 2.2 stuff and use the 2.0 that came with your Linux. It "just
works" out-of-the-box, and you can get better support / that way.

It's likely that there are config options for 2.2 that won't work with,
or might break, 2.0 Merging those files would be a Really Bad Idea.

--
* John Oliver http://www.john-oliver.net/ *