Ticket #575 (defect)
Opened 2 years ago
Last modified 2 years ago
mod_python test not tailored to UNIX
Status: new
| Reported by: | lawouach | Assigned to: | lawouach |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | CherryPy code | Keywords: | |
| Cc: |
Whenn running a test like this:
python test.py --server=modpygw
Under Linux it will fail for a couple of reasons:
- the "-k start" token is not a valid one for Apache under Linux. It is a Windows specific one I think.
- the configuration in modpy.py will not work because the path to mod_python.so is relative to the test directory and of course apache/apache2 can't find it there. Using the absolute path to the modules directory does solve the issue but I'm not sure how easy it could be to find it from the test harness itself. *
- apache2 will attempt to write the logs into a logs directory which needs to be created relatively to the test directory or the test will fail
In fact all the different files apache is looking for will cause the test to fail. For instance:
No such file or directory: could not open mime types config file /etc/apache2/mime.types. Configuration Failed
* Interestingly under Meppis (I assume Ubuntu-like) there is the following file:
/etc/apache2/mods-available/mod_python.load
which provides the correct directive with the full path to the mod_python module.
I cannot test further now but I will have al ook asap.
Change History
09/27/06 16:06:12: Modified by lawouach
- priority changed from high to normal.
- milestone deleted.
12/03/06 05:41:23: Modified by fumanchu
- summary changed from mod_python test failure to mod_python test not tailored to UNIX.

