The latter. It makes little sense. If it’s ignored then there’s no sense in having it.

Much like how the current `nginx -t` report makes little sense as well:

nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
nginx: [emerg] open() "/var/run/nginx.pid" failed (13: Permission denied)
nginx: configuration file /usr/local/etc/nginx/nginx.conf test failed

This basically says “config file is fine. I can’t read the pid file, even though I’ve been given permission to. the config file failed."


> On Jul 14, 2017, at 10:58 PM, Francis Daly <francis@daoine.org> wrote:
>
> If you are reporting that you invoke "nginx" as the super-user ("root")
> and it ignores the "user" directive in nginx.conf, that sounds to me
> like a bug that should be raised.
>
> If you are reporting that you invoke "nginx" as a non-root user, and it
> warns that the "user" directive in nginx.conf will be ignored, that is
> the expected behaviour.


_____________
Rich in Toronto @ VP






_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx