Yeah I was wrong, the doc says that if u only set the user and not the
group, then the group used has the same name than the user:
http://wiki.nginx.org/CoreModule#user
You are in the particular case so you didn't see anything ;o)

That would be probably better with the enhancement, since Nginx will
effectively check which group is really the primary one of the user...
---
*B. R.*


On Fri, May 11, 2012 at 12:56 PM, Edho Arief <edho@myconan.net> wrote:

> On Fri, May 11, 2012 at 11:25 PM, B.R. <reallfqq-nginx@yahoo.fr> wrote:
> > Did you specify the www-data group in the 'user' configuration entry of
> > Nginx?
> > If you did so then this is why. It is what you shall do at the present
> time
> > to allow group privileges to the worker processes.
> >
> > I only specified the user 'nginx' and not any group, since I thought the
> > groups which nginx belongs to would could automatically be used for
> access
> > privileges.
> > Maxim added a comment on the ticket and flagged it as a potential
> > enhancement, look at his comment: http://trac.nginx.org/nginx/ticket/165
> >
>
> I don't set anything, actually :/ (and I usually use same group name
> as username which probably explains why I never encountered this)
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx