| Summary: | Issues with mod_cband | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michael Stewart (vericgar) (RETIRED) <vericgar> |
| Component: | [OLD] Server | Assignee: | Krzysztof Pawlik (RETIRED) <nelchael> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | apache-bugs, jakub |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
files/10_mod_cband.conf
files/10_mod_cband.conf |
||
|
Description
Michael Stewart (vericgar) (RETIRED)
2006-03-07 22:33:45 UTC
Created attachment 81675 [details] files/10_mod_cband.conf (In reply to comment #0) > mod_cband does not have a reasonable default config - all it does is load the > module. At the minimum you should enable the status indicators. It would be > best if you put the example configurations in the module configuration. Comment > it out if you can't get it to work in a reasonable default way. Most of mod_cband configuration goes to per-vhost files, so it's only possible to have some simple example in 10_mod_cband.conf, I'm attaching a modified version of that file - is this version better? > Also, when I tried installing it to see what it was about, it failed miserably. > It tried to use apxs, when it should use apxs2. I took a look at the ebuild, > and it appears it's using it's own ./configure and Makefile instead of using > the eclass to compile it. I've made some changes in CVS so that it compiles and > installs correctly using the eclass. Please review my changes, and let me know > if you don't understand them, or would like to discuss them further. Thanks. > Also, if you are going to maintain an apache module, it's highly suggested that > your join the herd and bugzilla alias. Done. Kinda nitpicking, but - please, use example.com (net,org) in examples - using default Gentoo location for DocumentRoot would be nice as well. Like: # DocumentRoot /var/www/example.com # ServerName vhost1.example.com More nitpicking :)
Most of our module configuration files have a similar format as far as the IfDefine and IfModules go, generally like so:
<IfDefine MODNAME>
<IfModule !mod_modname.c>
LoadModule ....
</IfModule>
</IfDefine>
<IfModule mod_modname.c>
...
</IfModule>
This is done like this mostly so that if the user has added a LoadModule line elsewhere this config doesn't cause an error about a module being loaded twice. It also enables the default module configuration if the module is loaded, instead of it depending on the -D MODNAME being enabled.
Created attachment 82308 [details]
files/10_mod_cband.conf
New version - is it ok?
Much better! Thanks! Commited. |