Re: Apache built correctly?

[T Kellers]

Thank Mike,

It certainly helped me; I noticed the tcp6 thing, but hadn't had time to chase 
down the documentation.

Tim Kellers
CPE/NJIT
On Wednesday 05 February 2003 07:05 pm, Mike Loiterman wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wednesday, February 05, 2003 5:28 PM Matthew Emmerton 
 wrote:
> >> On Wednesday, February 05, 2003 10:31 AM [EMAIL PROTECTED]
> >
> >  wrote:
> >>> "Mike Loiterman" <[EMAIL PROTECTED]> writes:
>  On Tuesday, February 04, 2003 9:11 AM [EMAIL PROTECTED]
> 
>   wrote:
> > "Mike Loiterman" <[EMAIL PROTECTED]> writes:
> >> Absolutly nothing appears in the httpd-access.log file when I
> >> try to access the index.html.
> >>
> >> When I try to do http://localhost I get nothing.  Just this:
> >> unable to connect to remote host.
> >>
> >> I've restarted apache many times with the same results.  I
> >> restarted my machine with the same results.
> >>
> >> I can telnet into port 80 but Apache doesn't appear to answer.
> >> Something tells me that the daemon isn't running correctly or
> >> that Apache was installed incorrectly, although 'ps -aux | grep
> >> httpd' shows:
> >
> > What does "doesn't appear to answer" mean?  The fact that you can
> > telnet in tells you that it isn't a network-layer issue.  Did you
> > try a legitimate HTTP request?
> 
>  Well I telnet to 80 and it just says refused:
> 
>  [02:22:47 root@little_boy: /etc/mail]# telnet localhost 80 Trying
>  127.0.0.1... telnet: connect to address 127.0.0.1: Connection
>  refused telnet: Unable to connect to remote host
> >>>
> >>> Ah.  So you *can't* telnet into port 80.  That's different.
> >>> Use sockstat(1) to see if anything is bound to port 80, and look at
> >>> firewall rules to see if something's blocking it before it gets
> >>> there.
> >>
> >> [13:41:19 root@little_boy: /etc/mail]# sockstat | grep 80
> >> www  httpd  30322 3  tcp6   *:80  *:*
> >> www  httpd  30321 3  tcp6   *:80  *:*
> >> www  httpd  30320 3  tcp6   *:80  *:*
> >> www  httpd  30319 3  tcp6   *:80  *:*
> >> www  httpd  30318 3  tcp6   *:80  *:*
> >> root httpd  30309 3  tcp6   *:80  *:*
> >>
> >> Hrmm...seems to be bound to thr right ports???  I'm not sure how to
> >> check
> >
> > the firewall rules, as this machine is already behind a firewall.
> > Even so, wouldn't the http://localhost bypass any firewall stuff?
> >
> > It's bound to the right ports, but it's only listening on the IPv6
> > address -- not the IPv4 address.  I'm not sure what the fix for this
> > is, but this has been discussed on the list recently -- check the
> > archives.
>
> Matt:
> You were 100% on the mark.
>
> For anyone that is interested -- just add the following lines in your
> httpd.conf file:
>
> Listen 0.0.0.0:80
> Listen [::]:80
>
> And it works perfectly.  This is a known problem with Apache2 although it
> isn't well documented.  Hopefully this will help someone else.
>
> - ---
> Randomly Generated Quote:
> My phone number is seventeen. I got
> one of the early ones. --George Carlin
>
> Mike Loiterman
> PGP Key 0xD1B9D18E
> http://www.ascendency.net
>
>
>
> -BEGIN PGP SIGNATURE-
> Version: PGP 8.0
> Comment: This message has been digitally signed by Mike Loiterman
>
> iQA/AwUBPkGmvGjZbUnRudGOEQJu5wCghdp1njU/6Y35/kZhXFv2r9VweNMAn0D/
> uDnpEC797YOoAQ8WBKwBYDKZ
> =AraT
> -END PGP SIGNATURE-
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

RE: Apache built correctly?

[Mike Loiterman]

 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, February 05, 2003 5:28 PM Matthew Emmerton  
wrote:

>> On Wednesday, February 05, 2003 10:31 AM [EMAIL PROTECTED]
>  wrote:
>> 
>>> "Mike Loiterman" <[EMAIL PROTECTED]> writes:
>>> 
 
 On Tuesday, February 04, 2003 9:11 AM [EMAIL PROTECTED]
  wrote:
 
> "Mike Loiterman" <[EMAIL PROTECTED]> writes:
> 
>> Absolutly nothing appears in the httpd-access.log file when I
>> try to access the index.html. 
>> 
>> When I try to do http://localhost I get nothing.  Just this:
>> unable to connect to remote host.
>> 
>> I've restarted apache many times with the same results.  I
>> restarted my machine with the same results.
>> 
>> I can telnet into port 80 but Apache doesn't appear to answer.
>> Something tells me that the daemon isn't running correctly or
>> that Apache was installed incorrectly, although 'ps -aux | grep
>> httpd' shows:
> 
> What does "doesn't appear to answer" mean?  The fact that you can
> telnet in tells you that it isn't a network-layer issue.  Did you
> try a legitimate HTTP request?
 
 Well I telnet to 80 and it just says refused:
 
 [02:22:47 root@little_boy: /etc/mail]# telnet localhost 80 Trying
 127.0.0.1... telnet: connect to address 127.0.0.1: Connection
 refused telnet: Unable to connect to remote host
>>> 
>>> Ah.  So you *can't* telnet into port 80.  That's different.
>>> Use sockstat(1) to see if anything is bound to port 80, and look at
>>> firewall rules to see if something's blocking it before it gets
>>> there. 
>> 
>> [13:41:19 root@little_boy: /etc/mail]# sockstat | grep 80
>> www  httpd  30322 3  tcp6   *:80  *:*
>> www  httpd  30321 3  tcp6   *:80  *:*
>> www  httpd  30320 3  tcp6   *:80  *:*
>> www  httpd  30319 3  tcp6   *:80  *:*
>> www  httpd  30318 3  tcp6   *:80  *:*
>> root httpd  30309 3  tcp6   *:80  *:*
>> 
>> Hrmm...seems to be bound to thr right ports???  I'm not sure how to
>> check 
> the firewall rules, as this machine is already behind a firewall. 
> Even so, wouldn't the http://localhost bypass any firewall stuff?
> 
> It's bound to the right ports, but it's only listening on the IPv6
> address -- not the IPv4 address.  I'm not sure what the fix for this
> is, but this has been discussed on the list recently -- check the
> archives. 

Matt:
You were 100% on the mark.

For anyone that is interested -- just add the following lines in your httpd.conf file:

Listen 0.0.0.0:80
Listen [::]:80

And it works perfectly.  This is a known problem with Apache2 although it isn't well 
documented.  Hopefully this will help someone else.

- ---
Randomly Generated Quote:
My phone number is seventeen. I got
one of the early ones. --George Carlin

Mike Loiterman
PGP Key 0xD1B9D18E
http://www.ascendency.net



-BEGIN PGP SIGNATURE-
Version: PGP 8.0
Comment: This message has been digitally signed by Mike Loiterman

iQA/AwUBPkGmvGjZbUnRudGOEQJu5wCghdp1njU/6Y35/kZhXFv2r9VweNMAn0D/
uDnpEC797YOoAQ8WBKwBYDKZ
=AraT
-END PGP SIGNATURE-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: Apache built correctly?

[Matthew Emmerton]

> On Wednesday, February 05, 2003 10:31 AM [EMAIL PROTECTED]
 wrote:
>
> > "Mike Loiterman" <[EMAIL PROTECTED]> writes:
> >
> >>
> >> On Tuesday, February 04, 2003 9:11 AM [EMAIL PROTECTED]
> >>  wrote:
> >>
> >>> "Mike Loiterman" <[EMAIL PROTECTED]> writes:
> >>>
>  Absolutly nothing appears in the httpd-access.log file when I try
>  to access the index.html.
> 
>  When I try to do http://localhost I get nothing.  Just this:
>  unable to connect to remote host.
> 
>  I've restarted apache many times with the same results.  I
>  restarted my machine with the same results.
> 
>  I can telnet into port 80 but Apache doesn't appear to answer.
>  Something tells me that the daemon isn't running correctly or that
>  Apache was installed incorrectly, although 'ps -aux | grep httpd'
>  shows:
> >>>
> >>> What does "doesn't appear to answer" mean?  The fact that you can
> >>> telnet in tells you that it isn't a network-layer issue.  Did you
> >>> try a legitimate HTTP request?
> >>
> >> Well I telnet to 80 and it just says refused:
> >>
> >> [02:22:47 root@little_boy: /etc/mail]# telnet localhost 80 Trying
> >> 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused
> >> telnet: Unable to connect to remote host
> >
> > Ah.  So you *can't* telnet into port 80.  That's different.
> > Use sockstat(1) to see if anything is bound to port 80, and look at
> > firewall rules to see if something's blocking it before it gets there.
>
> [13:41:19 root@little_boy: /etc/mail]# sockstat | grep 80
> www  httpd  30322 3  tcp6   *:80  *:*
> www  httpd  30321 3  tcp6   *:80  *:*
> www  httpd  30320 3  tcp6   *:80  *:*
> www  httpd  30319 3  tcp6   *:80  *:*
> www  httpd  30318 3  tcp6   *:80  *:*
> root httpd  30309 3  tcp6   *:80  *:*
>
> Hrmm...seems to be bound to thr right ports???  I'm not sure how to check
the firewall rules, as this machine is already behind a firewall.  Even so,
wouldn't the http://localhost bypass any firewall stuff?

It's bound to the right ports, but it's only listening on the IPv6
address -- not the IPv4 address.  I'm not sure what the fix for this is, but
this has been discussed on the list recently -- check the archives.

--
Matt Emmerton


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

RE: Apache built correctly?

[Mike Loiterman]

 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, February 05, 2003 10:31 AM [EMAIL PROTECTED] 
 wrote:

> "Mike Loiterman" <[EMAIL PROTECTED]> writes:
> 
>> 
>> On Tuesday, February 04, 2003 9:11 AM [EMAIL PROTECTED]
>>  wrote: 
>> 
>>> "Mike Loiterman" <[EMAIL PROTECTED]> writes:
>>> 
 Absolutly nothing appears in the httpd-access.log file when I try
 to access the index.html. 
 
 When I try to do http://localhost I get nothing.  Just this:
 unable to connect to remote host.
 
 I've restarted apache many times with the same results.  I
 restarted my machine with the same results.
 
 I can telnet into port 80 but Apache doesn't appear to answer.
 Something tells me that the daemon isn't running correctly or that
 Apache was installed incorrectly, although 'ps -aux | grep httpd'
 shows:
>>> 
>>> What does "doesn't appear to answer" mean?  The fact that you can
>>> telnet in tells you that it isn't a network-layer issue.  Did you
>>> try a legitimate HTTP request?
>> 
>> Well I telnet to 80 and it just says refused:
>> 
>> [02:22:47 root@little_boy: /etc/mail]# telnet localhost 80 Trying
>> 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused
>> telnet: Unable to connect to remote host
> 
> Ah.  So you *can't* telnet into port 80.  That's different.
> Use sockstat(1) to see if anything is bound to port 80, and look at
> firewall rules to see if something's blocking it before it gets there.

[13:41:19 root@little_boy: /etc/mail]# sockstat | grep 80
www  httpd  30322 3  tcp6   *:80  *:*
www  httpd  30321 3  tcp6   *:80  *:*
www  httpd  30320 3  tcp6   *:80  *:*
www  httpd  30319 3  tcp6   *:80  *:*
www  httpd  30318 3  tcp6   *:80  *:*
root httpd  30309 3  tcp6   *:80  *:*

Hrmm...seems to be bound to thr right ports???  I'm not sure how to check the firewall 
rules, as this machine is already behind a firewall.  Even so, wouldn't the 
http://localhost bypass any firewall stuff?

- ---
Randomly Generated Quote:
Useless Invention: Brown undershorts.

Mike Loiterman
PGP Key 0xD1B9D18E
http://www.ascendency.net



-BEGIN PGP SIGNATURE-
Version: PGP 8.0
Comment: This message has been digitally signed by Mike Loiterman

iQA/AwUBPkGTFGjZbUnRudGOEQLotgCcDS5LT030EiupOSQ7vOwQRa/ytJMAnA9R
ehJvztUVn8vsxwsdbSxVuJKV
=JogU
-END PGP SIGNATURE-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

RE: Apache built correctly?

[Mike Loiterman]

 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, February 05, 2003 10:31 AM [EMAIL PROTECTED] 
 wrote:

> "Mike Loiterman" <[EMAIL PROTECTED]> writes:
> 
>> 
>> On Tuesday, February 04, 2003 9:11 AM [EMAIL PROTECTED]
>>  wrote: 
>> 
>>> "Mike Loiterman" <[EMAIL PROTECTED]> writes:
>>> 
 Absolutly nothing appears in the httpd-access.log file when I try
 to access the index.html. 
 
 When I try to do http://localhost I get nothing.  Just this:
 unable to connect to remote host.
 
 I've restarted apache many times with the same results.  I
 restarted my machine with the same results.
 
 I can telnet into port 80 but Apache doesn't appear to answer.
 Something tells me that the daemon isn't running correctly or that
 Apache was installed incorrectly, although 'ps -aux | grep httpd'
 shows:
>>> 
>>> What does "doesn't appear to answer" mean?  The fact that you can
>>> telnet in tells you that it isn't a network-layer issue.  Did you
>>> try a legitimate HTTP request?
>> 
>> Well I telnet to 80 and it just says refused:
>> 
>> [02:22:47 root@little_boy: /etc/mail]# telnet localhost 80 Trying
>> 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused
>> telnet: Unable to connect to remote host
> 
> Ah.  So you *can't* telnet into port 80.  That's different.
> Use sockstat(1) to see if anything is bound to port 80, and look at
> firewall rules to see if something's blocking it before it gets there.

[13:41:19 root@little_boy: /etc/mail]# sockstat | grep 80
www  httpd  30322 3  tcp6   *:80  *:*
www  httpd  30321 3  tcp6   *:80  *:*
www  httpd  30320 3  tcp6   *:80  *:*
www  httpd  30319 3  tcp6   *:80  *:*
www  httpd  30318 3  tcp6   *:80  *:*
root httpd  30309 3  tcp6   *:80  *:*

Hrmm...seems to be bound to thr right ports???  I'm not sure how to check the firewall 
rules, as this machine is already behind a firewall.  Even so, wouldn't the 
http://localhost bypass any firewall stuff?

- ---
Randomly Generated Quote:
'Try to keep things in perspective.
Fifty years from now, kids in history
classes will be yawning over what
panics us today.' -- Unknown

Mike Loiterman
PGP Key 0xD1B9D18E
http://www.ascendency.net



-BEGIN PGP SIGNATURE-
Version: PGP 8.0
Comment: This message has been digitally signed by Mike Loiterman

iQA/AwUBPkFof2jZbUnRudGOEQJ/iQCfa3x7TM7tF7RQCgF+kN1wjxnuk8gAoOjI
qmXBlK/oxeZBw08G6dnTXkYP
=szb4
-END PGP SIGNATURE-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: Apache built correctly?

[Lowell Gilbert]

"Mike Loiterman" <[EMAIL PROTECTED]> writes:

>  
> On Tuesday, February 04, 2003 9:11 AM [EMAIL PROTECTED] 
> wrote:
> 
> > "Mike Loiterman" <[EMAIL PROTECTED]> writes:
> > 
> >> Absolutly nothing appears in the httpd-access.log file when I try to
> >> access the index.html. 
> >> 
> >> When I try to do http://localhost I get nothing.  Just this:
> >> unable to connect to remote host.
> >> 
> >> I've restarted apache many times with the same results.  I restarted
> >> my machine with the same results. 
> >> 
> >> I can telnet into port 80 but Apache doesn't appear to answer. 
> >> Something tells me that the daemon isn't running correctly or that
> >> Apache was installed incorrectly, although 'ps -aux | grep httpd'
> >> shows:   
> > 
> > What does "doesn't appear to answer" mean?  The fact that you can
> > telnet in tells you that it isn't a network-layer issue.  Did you try
> > a legitimate HTTP request?
> 
> Well I telnet to 80 and it just says refused:
> 
> [02:22:47 root@little_boy: /etc/mail]# telnet localhost 80
> Trying 127.0.0.1...
> telnet: connect to address 127.0.0.1: Connection refused
> telnet: Unable to connect to remote host

Ah.  So you *can't* telnet into port 80.  That's different.
Use sockstat(1) to see if anything is bound to port 80, and look at
firewall rules to see if something's blocking it before it gets there.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

RE: Apache built correctly?

[Mike Loiterman]

 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday, February 04, 2003 9:11 AM [EMAIL PROTECTED] 
 wrote:

> "Mike Loiterman" <[EMAIL PROTECTED]> writes:
> 
>> Absolutly nothing appears in the httpd-access.log file when I try to
>> access the index.html. 
>> 
>> When I try to do http://localhost I get nothing.  Just this:
>> unable to connect to remote host.
>> 
>> I've restarted apache many times with the same results.  I restarted
>> my machine with the same results. 
>> 
>> I can telnet into port 80 but Apache doesn't appear to answer. 
>> Something tells me that the daemon isn't running correctly or that
>> Apache was installed incorrectly, although 'ps -aux | grep httpd'
>> shows:   
> 
> What does "doesn't appear to answer" mean?  The fact that you can
> telnet in tells you that it isn't a network-layer issue.  Did you try
> a legitimate HTTP request?

Well I telnet to 80 and it just says refused:

[02:22:47 root@little_boy: /etc/mail]# telnet localhost 80
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
telnet: Unable to connect to remote host

- ---
Randomly Generated Quote:
'The problem with people who have no
vices is that generally you can be
pretty sure they're going to have some
pretty annoying virtues.' -- Elizabeth
Taylor

Mike Loiterman
PGP Key 0xD1B9D18E
http://www.ascendency.net



-BEGIN PGP SIGNATURE-
Version: PGP 8.0
Comment: This message has been digitally signed by Mike Loiterman

iQA/AwUBPkDKYmjZbUnRudGOEQKoEQCgl5omE1DqQQ6t5saLS01AyUnnRUAAnjBX
w0H24Qy+ddwA7vMo3olQhr+D
=jVQi
-END PGP SIGNATURE-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: Apache built correctly?

[Lowell Gilbert]

"Mike Loiterman" <[EMAIL PROTECTED]> writes:

> Absolutly nothing appears in the httpd-access.log file when I try to access the 
>index.html.
> 
> When I try to do http://localhost I get nothing.  Just this:
> unable to connect to remote host.
> 
> I've restarted apache many times with the same results.  I restarted my machine with 
>the same results.  
> 
> I can telnet into port 80 but Apache doesn't appear to answer.  Something tells me 
>that the daemon isn't running correctly or that Apache was installed incorrectly, 
>although 'ps -aux | grep httpd' shows:

What does "doesn't appear to answer" mean?  The fact that you can
telnet in tells you that it isn't a network-layer issue.  Did you try
a legitimate HTTP request?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: Apache built correctly?

[Tim Kellers]

After starting the program, check httpd with netstat and sockstat: I found, 
astonishingly enough, that tcp4 httpd wasn't running, but tcp6 httpd was 
chugging along fine.  I didn't have time to scour the documentation (my 
5.0-CURRENT machine is an alpha machine), so I installed apache 1.3.2.7 and 
tcp4 worked yet again.

If anyone points you (and me) to the corrrect documentation describing this 
change in apache; I'll be happy to read it.

Tim Kellers
CPE/NJIT


On Monday 03 February 2003 09:06 am, Mike Loiterman wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I realize that this is not the Apache mailing list, but I've posted this
> three times on the Apache list and have not gotten a single reply.  At this
> point, I have to assume that this is some amazingly complex error (pretty
> unlikely), or one that is related to FreeBSD 5.0 and not really a problem
> with Apache.  In any event, I'm submitting it here in the hopes that
> someone can either help solve my issue or point me to anthor source of
> Apache assistance.
>
>
>
> Just built Apache 2.0.43 in ports, but having trouble getting it to work
> correctly.
>
> Apache seems to start fine with the tradtional FreeBSD command: apachectl
> start.  There are no errors in http-error.log.  Just this: Apache/2.0.43
> (Unix) configured -- resuming normal operations
>
> Absolutly nothing appears in the httpd-access.log file when I try to access
> the index.html.
>
> When I try to do http://localhost I get nothing.  Just this:
> unable to connect to remote host.
>
> I've restarted apache many times with the same results.  I restarted my
> machine with the same results.
>
> I can telnet into port 80 but Apache doesn't appear to answer.  Something
> tells me that the daemon isn't running correctly or that Apache was
> installed incorrectly, although 'ps -aux | grep httpd' shows:
>
> root  19105  0.0  6.6  4128 2864  ??  Ss1:00AM   0:00.12
> /usr/local/sbin/httpd -k start www   19106  0.0  6.6  4144 2848  ??  S
> 1:00AM   0:00.02 /usr/local/sbin/httpd -k start www   19107  0.0  6.6  4144
> 2848  ??  S 1:00AM   0:00.02 /usr/local/sbin/httpd -k start www   19108
>  0.0  6.6  4144 2848  ??  S 1:00AM   0:00.02 /usr/local/sbin/httpd -k
> start www   19109  0.0  6.6  4144 2848  ??  S 1:00AM   0:00.02
> /usr/local/sbin/httpd -k start www   19110  0.0  6.6  4144 2848  ??  S
> 1:00AM   0:00.02 /usr/local/sbin/httpd -k start root  19114  0.0  0.4   284
>  156  p0  R+1:00AM   0:00.01 grep httpd
>
> I'm not sure what -k is.  I couldn't find any mention of it in the manual.
>
> I haven't changed anything in the httpd.conf file other then the servername
> and the serveradmin. Its basically a default install. I've tried different
> ports and different server names including localhost, but none seem to
> work.
>
> Here is my httpd.conf file:
> #
> # Based upon the NCSA server configuration files originally by Rob McCool.
> #
> # This is the main Apache server configuration file.  It contains the
> # configuration directives that give the server its instructions.
> # See http://httpd.apache.org/docs-2.0/> for detailed information
> about # the directives.
> #
> # Do NOT simply read the instructions in here without understanding
> # what they do.  They're here only as hints or reminders.  If you are
> unsure # consult the online docs. You have been warned.
> #
> # The configuration directives are grouped into three basic sections:
> #  1. Directives that control the operation of the Apache server process as
> a # whole (the 'global environment').
> #  2. Directives that define the parameters of the 'main' or 'default'
> server, # which responds to requests that aren't handled by a virtual
> host. # These directives also provide default values for the settings #
> of all virtual hosts.
> #  3. Settings for virtual hosts, which allow Web requests to be sent to
> # different IP addresses or hostnames and have them handled by the
> # same Apache server process.
> #
> # Configuration and logfile names: If the filenames you specify for many
> # of the server's control files begin with "/" (or "drive:/" for Win32),
> the # server will use that explicit path.  If the filenames do *not* begin
> # with "/", the value of ServerRoot is prepended -- so "/var/log/foo.log" #
> with ServerRoot set to "/usr/local" will be interpreted by the
> # server as "/usr/local//var/log/foo.log".
> #
>
> ### Section 1: Global Environment
> #
> # The directives in this section affect the overall operation of Apache,
> # such as the number of concurrent requests it can handle or where it
> # can find its configuration files.
> #
>
> #
> # ServerRoot: The top of the directory tree under which the server's
> # configuration, error, and log files are kept.
> #
> # NOTE!  If you intend to place this on an NFS (or otherwise network)
> # mounted filesystem then please read the LockFile documentation (available
> # at http://httpd.apache.org/docs-2.0/mod