[Supervisor-users] [Fwd: Re: FastCGI - socket not being created with correct user]
Chris McDonough
chrism at plope.com
Mon Oct 19 03:24:53 EDT 2009
Somehow my mail client managed to not sent this to the list.
-------- Original Message --------
Subject: Re: [Supervisor-users] FastCGI - socket not being created with correct
user
Date: Mon, 19 Oct 2009 03:24:00 -0400
From: Chris McDonough <chrism at plope.com>
To: phill at activityhq.com
CC: List at laguna.palladion.com:Supervisord
<supervisor-users at lists.supervisord.org>, Mailing at laguna.palladion.com
References: <4AD846F6.6030504 at activityhq.com> <4AD8A075.1040006 at plope.com>
<4ADC1280.8060908 at activityhq.com>
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:
>
> [root at 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
> Supervisor-users at lists.supervisord.org
> http://lists.supervisord.org/mailman/listinfo/supervisor-users
>
_______________________________________________
Supervisor-users mailing list
Supervisor-users at lists.supervisord.org
http://lists.supervisord.org/mailman/listinfo/supervisor-users
More information about the Supervisor-users
mailing list