Re: Virutal Host and ServerName with ports...

Ryan Bloom wrote: Hi. The big thing about ServerName in 2.0 is that it has taken over for the Port directive from 1.3. So, the following config means that the server listens on 127.0.0.1, port 8080, but reports itself as foo.com on port 80. VirtualHost 127.0.0.1:8080 ServerName

Re: mod_webapp fails to build

Andrew Savory wrote: jean-frederic clere wrote: I am afraid that is my fault... Heh. No problem, I'd be happy to post suggestions for revising readme.txt/install.txt once I'm up and running! I think your apxs is broken, what does the following commands return? /usr/bin/apxs -q

[PATCH] Check the mpm exists when using --with-mpm=MPM

Jeff Trawick wrote: jean-frederic clere [EMAIL PROTECTED] writes: What should I use now? worker or perchild As it says in CHANGES... *) The threaded MPM for Unix has been removed. Use the worker MPM instead. [various] Would it be possible to check the given parameter

apxs broken

Hi, I have noted that apxs is broken: /home/apache20/apache20/bin/apxs -q PREFIX apxs:Error: 100 100exec_prefix)/bin/httpd not found or not executable. Any hints? Cheers Jean-frederic

Re: apxs broken

Stas Bekman wrote: On Thu, 6 Sep 2001, jean-frederic clere wrote: Hi, I have noted that apxs is broken: /home/apache20/apache20/bin/apxs -q PREFIX apxs:Error: 100 100exec_prefix)/bin/httpd not found or not executable. Any hints? what version are you trying to use? Get

Re: apxs broken

) instead of ${foo}, of course this completely breaks apxs. So the fix is to put back the code that was generating ${foo} and not $(foo). Unless somebody wants it that way ($(foo)) and then apxs needs to be adjusted. On Thu, 6 Sep 2001, jean-frederic clere wrote: The problem

<    1   2   3   4   5