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 Phillip Oldham wrote: > Supervisord is being started as root, and the `user` param is being set: > > [fcgi-program:php] > command=/usr/bin/php-cgi > socket=unix:///tmp/php.sock > process_name=%(program_name)s_%(process_num)02d > numprocs=4 > user=nginx > environment=PHP_FCGI_MAX_REQUESTS=50,PHP_FCGI_CHILDREN=4 > > but the socket/file (/tmp/php.sock) is created as root: > > [r...@rezbot ~]# ls -alh /tmp > ... > srwxr-xr-x 1 root root 0 Oct 17 08:22 php.sock > ... > > any suggestions, other than setting it to listen on a port instead? > _______________________________________________ > 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
