What you described in your previous email should have worked. I'm not sure if this is a bug, or what.
- C Phillip Oldham wrote: > Chris McDonough wrote: >> There is a separate "user" parameter that is set in the [supervisord] section >> that may help you work around the issue. The entire supervisord process (and >> any children, and any socket files) will be run/written using that userid. >> >> [supervisord] >> user = nginx >> >> Please read >> http://supervisord.org/manual/current/configuration.html#supervisord >> > Thanks. I'll see if I can get that to work. > > However, is there a way to have supervisord run as root, yet have the > socket created by another user? eg: > > [supervisord] > user = root > ... > [fcgi-program:php] > user = nginx > socket = unix:///tmp/php.sock > ... > _______________________________________________ > Supervisor-users mailing list > [email protected] > http://lists.supervisord.org/mailman/listinfo/supervisor-users > _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
