On Thu, Oct 21, 2010 at 11:58 PM, Graham Dumpleton <[email protected]> wrote: > I have started to accumulate a description of these in a special > document. It can now be found at: > > http://code.google.com/p/modwsgi/wiki/CheckingYourInstallation > > I'll add more as I remember them or have to tell people special checks > to do. If you think of any that should go in there, let me know. Also > let me know if you think stuff in there is confusing or could do with > a better explanation.
This looks to be a useful document. Here's some of my comments, mostly to provide perspective for Linux installations, and especially yum/rpm-based distros (Fedora, etc.) First, you may want to link to the classic document "How to Ask Questions the Smart Way" -- your call. See http://www.catb.org/esr/faqs/smart-questions.html (1) I think perhaps the first thing that people seeking help should provide should be the big-picture obvious things, but unfortunately are often omitted. These are the things I would want people to always give: a) What operating system. If Linux, also include the output of: cat /etc/system-release If Unix-like, include the output of: uname -a b) Are you using the system-provided executables, or has the user attempted to compile from source? This includes: Apache httpd Python mod_wsgi For RPM-based Linux systems, also include the output of: rpm -qa mod_\* httpd\* python c) If running Linux, are the SElinux security extensions being used? Include the output of running: sestatus [Perhaps we might some day need a lot more on using mod_wsgi in an SElinux environment, as more and more people seem to be getting bit by it as SElinux is becoming the default install. I can perhaps help with documenting that ???] (3) The part about examining the apxs script to locate a config.nice file could be too challenging. Under Fedora 13 for instance, parts of the apxs script look like: ... my $libdir = `pkg-config --variable=libdir apr-1`; chomp $libdir; my $installbuilddir = $libdir . "/httpd/build"; ... which if you don't know Perl and don't know about pkg-config (a Red Hat invention), then you'd be hard pressed to figure out the build dir. BTW, under Fedora it will be one of these depending on whether you're 32- or 64-bit: /usr/lib/httpd/build/ /usr/lib64/httpd/build/ Furthermore, there's not even a config.nice file at all. Instead, being RPM based, to see how Apache was built you have to get the SRPM file (Source RPM), which contains all the configure and make options. So, under RPM linuxes, getting this is going to be problematic, or at least quite a bit more complicated. Instead, under such cases, I'd suggest that the user at least provide the rpm package details and distro version [as I suggested under (1) above, by running "rpm -qi httpd" and "cat /etc/system-release"] (4) When looking for the header apr.h, if you're under a RPM Linux, you may need to install the (optional) development packages, and specifically the apr-devel package. -- Deron Meranda http://deron.meranda.us/ -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
