I think I've figured out why this was happening. If Server.app can't parse 
a configuration file when it starts up, it replaces the unreadable file 
with a default file while leaving Apache running on its previous config. 
When that happens, restarting the web service causes the new default 
setting to take effect even though days might have passed since you opened 
Server.app. I would call it a bug.

This is all very confusing, but the reason for it is that Apple's vision 
for Apache is to eventually have all configuration files in *.plist format. 
The shift from *.conf to plist has been gradual and at this time is a 
combination of both filetypes. I still don't fully understand how it all 
works and anything I said in previous posts should be taken as guesswork.

My webapp has been running normally for about 24 hours, so I assume the 
problem is fixed. So it turns out to NOT be a Python or WSGI problem. Thank 
you for your patience, hopefully my experimenting is helpful to someone.

-- Gnarlie
<http://gnarlodious.com/> <http://gnarlodious.com/>

http://Gnarlodious.com

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/modwsgi/-/sxaoxFTKaL4J.
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.

Reply via email to