|
From: Gilles D. <gr...@sc...> - 2003-06-12 20:37:32
|
As far as I know, Apache has always allowed putting all access.conf and srm.conf directives right in httpd.conf. The 3 file setup was a carryover from NCSA httpd, but I don't think Apache 1.x ever enforced any context-specific stuff in any of the files. With Apache 2, they've done away with the deprecated files. I think the portable way to configure Apache would be to put everything in httpd.conf, but put out empty srm.conf and access.conf files just to keep Apache 1 happy. According to Lachlan Andrew: > Excellent work, Jim! > > Could you please mail a list of the lines you commented out? It would > be really nice to have make check work "out of the box", and I > think most of the lines in *.conf are not necessary for any platform. > > The first warning was due to a (trivial) bug, and I'll also get rid of > the last. The other two seem harmless and platform-dependent, so > I'll leave them for now. > > Thanks for your detective work :) > Lachlan > > On Sun, 1 Jun 2003 12:04, Jim Cole wrote: > > I tested Friday's CVS on a Red Hat 8 system. > > > > I ran rundig against www.htdig.org using robotstxt_name: > > master-htdig and did not encounter any noticeable problems. The > > database sizes seemed reasonable and were searchable. > > > > Four of the tests fail outright and numerous errors are reported. > > Most of the problems are due to the fact that the httpd.conf file > > used is not entirely compatible with Apache 2. By merging > > httpd.conf, access.conf, and srm.conf into a single file and then > > commenting out everything that 'make check' complained about, I was > > able to get three of the four problematic tests to pass. -- Gilles R. Detillieux E-mail: <gr...@sc...> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) |