On Saturday, August 28, 2010, Dave Paola <[email protected]> wrote: > Hi all, > > I have a system where users upload wsgi applications and we serve them > using apache/mod_wsgi. For scaling reasons, we're simply using the > WSGIDaemonProcess directive and setting them to dynamically allocated > UID/GIDs. The problem is, we don't have associated users with these > UIDs. > > Is there a way to keep mod_wsgi from trying to determine the "user" > associated with a particular UID? I can't find a directive anywhere > that does this. > > Any ideas?
Is there any reason why you can't have an entry in /etc/passwd for that uid mapping to a dummy name, eg uXYZ, where XYX is the uid. You don't need to create an actual home directory or anything else, just have the passwd file entry be a no login account and a dummy home directory that doesn't exist either. As to you question, there might if changes are made to mod_wsgi code, but don't have code in front of me right now. More importantly I want to understand why you can't have that passwd file entry, as would be worried that various code will break in a Python application anyway if it doesn't exist, which would make any change pointless. Graham > Cheers, > Dave Paola > www.djangy.com > > -- > 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. > > -- 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.
