I've been doing some more work on this, and part of the problem
appears to be the relative position of the ServerName and WebApp*
directives. If the ServerName is declared above the WebApp* directive,
there are no complaints about the "invalid server name", but httpd now
doesn't start at all (though it claims to be when started via
apachectl)

Leaving the port off ServerName gives:

mite:/usr/local/apache-2# ./bin/apachectl start
Syntax error on line 222 of /usr/local/apache-2/conf/httpd.conf:
Invalid port number (p<1) No "Port" statement found
./bin/apachectl start: httpd could not be started
mite:/usr/local/apache-2# 

Restoring the port number to ServerName gives no error messages, but
httpd doesn't start, as I said. It turns out the httpd won't start if
any WebApp* declaration is given, but there are no log messages to
help trace the problem.

Has anyone else seen this?

Cheers,

Simon

-- 
"Make your girlfriend cry when you're having sex by phoning her"
    --- Viz top tip

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to