Yes, I've disabled it now, and all is good!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, se
Do you have SELinux enabled? Check /var/log/audit/audit.log and/or try
disabling it by editing /etc/sysconfig/selinux and rebooting.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to
> I started to rev back mod_python and ran into a few dependency problems. I'll
> keep trying and see if that helps. Will let you know...
The REAL problem between my working (openhosting.com virtual) Fedora
system and this one was SELinux. Aarrgghh!
And of course I didn't have any problems in s
Thanks for the replies everybody. This is good info and I need to know
more about apache in general.
Unfortunately it doesn't solve the problem! I am using the vanilla
Fedora rpm for httpd which builds in prefork.c and has generally
default module directives. The funny behaviour is that it runs f
On 4/21/06, Richie Hindle <[EMAIL PROTECTED]> wrote:
> For what it's worth, I think this advice should be in the documentation.
> The documentation says "Apache with mod_python currently is the preferred
> setup for using Django on a production server" but it doesn't explain
> which MPM.
Good cal
I've been running django (trunk and M-R) on apache prefork with no problems. I recently switched to the worker MPM, and so far, everything seems to work fine (with better memory usage, I might add). I did have a problem on a separate installation, however, related to memcache. I think there may
[Jacob]
> I'd suggest switching to the "prefork" MPM for Apache
For what it's worth, I think this advice should be in the documentation.
The documentation says "Apache with mod_python currently is the preferred
setup for using Django on a production server" but it doesn't explain
which MPM.
--
On Apr 21, 2006, at 12:06 AM, oggie rob wrote:
> Any ideas what I am facing here? Or how to debug this?
I'd suggest switching to the "prefork" MPM for Apache; I've always
seen better performance and stability running Django under it as
opposed to the threaded one. Don't know if that's you're
Hi all,
I have a problem with a new server that I am setting up.
Details are:
Fedora Core 5
apache httpd 2.2.0 (rpm)
postgresql 8.1.3 (rpm)
psycopg 1.1.21(source - and a real pain)
python 2.4 (rpm)
pretty weak hardware (800 mHz PIII, 256 M RAM)
So, this app runs fine on two other machines (simila
9 matches
Mail list logo
