Works like a charm now...thank you Graham!
On Sep 23, 11:52 pm, Graham Dumpleton <[email protected]>
wrote:
> You need to use WSGIProcessGroup directive in conjunction with
> WSGIDaemonProcess in order to delegate application to run in that
> process group. See simple examples in:
>
> http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide#Delegat...
>
> Graham
>
> 2009/9/24 Randy Syring <[email protected]>:
>
>
>
> > I am running modwsgi 2.5 on Apache 2.2.11 built against Python 2.5.4
> > in daemon mode. I have the the following config:
>
> >http://paste.pocoo.org/show/141217/
>
> > Everything seems to be working well except that the daemon processes
> > are still running as the user www-data, which is the ubuntu user the
> > apache child processes run under. I have confirmed that apache is
> > *started* as root since there is an apache process owned by root and
> > the log files are owned by root. However, the child processes do not
> > *run* as root.
>
> > Will this setup work to assign the modwsgi daemon processes their own
> > users? Or do the child processes need to run as root? If this setup
> > should work, any ideas why my current config is not working as
> > expected? I did turn on "LogLevel info" but did not see any useful
> > information there.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---