SOLVED.
Fixed the Apache problem... It was a directive that was
needed to tell apache how to look at /data/vhosts/:
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
On Wed, 9 Mar 2005 13:05:39 -0800, Benjamin Keating
<[EMAIL PROTECTED]> wrote:
I'm Running FreeBSD 5.3 and Apache2, compiled from Ports.
I'm setting up a series of VirtualHosts in Apache. Apache runs fine
otherwise. The vhosts that are not working are under:
/data/vhosts//{www,logs}/ (where /data/ is a single
filesystem on it's own harddrive). Here is a sample vhost entry:
Odhiambo Washington <[EMAIL PROTECTED]> writes:
> I am wondering why there are two apache2 ports commited to the
> ports tree.
>
> /usr/ports/www/apache2 and /usr/ports/www/apache21 are one and
> the same (unless I am on crack) so why have them?
The apache21 port is probabl
I am wondering why there are two apache2 ports commited to the
ports tree.
/usr/ports/www/apache2 and /usr/ports/www/apache21 are one and
the same (unless I am on crack) so why have them?
-Wash
http://www.netmeister.org/news/learn2quote.html
--
|\ _,,,---,,_ | Odhiambo
Hi,
I compiled apache2 like this in my ports dir [yes, my tree is up to
date]
-su-2.05b# cd /usr/ports/www/apache2/
-su-2.05b# make -DWITH_SUEXEC
-su-2.05b# cd work/httpd-2.0.46/
-su-2.05b# ./httpd -l
Compiled in modules:
core.c
prefork.c
http_core.c
mod_so.c
I notice that mod_suexec or
