Two little bugs

Mark Alan varia at
Wed Dec 8 18:52:11 MSK 2010

On Tue, 7 Dec 2010 10:38:26 +0300, Igor Sysoev <igor at> wrote:

> > 1. if the argument of nginx -c is a relative path, it wil trigger a
> > segment fault. Meant to be implemented like that? Because since
> > 0.5.x to current release contain this bug.
> Could you show a test case ?
> I can not reproduce the issue.

While using Ubuntu 10.10+Nginx 0.8.53

1. using full path works:
sudo nginx -c /etc/nginx/nginx.conf

2. using relative path fails:
sudo nginx -c nginx.conf
with error:
[emerg]: open() "/usr/local/nginx/nginx.conf" failed (2: No such file
or directory)

As seen bellow, my --conf-path=/etc/nginx/nginx.conf.
Why is nginx trying to open it at /usr/local/nginx/nginx.conf?
Is it hard wired at some other place in the code?



$ nginx -V
nginx version: nginx0.8.53
TLS SNI support enabled
configure arguments: --conf-path=/etc/nginx/nginx.conf
--lock-path=/var/lock/nginx.lock --pid-path=/var/run/
--with-http_ssl_module --without-http_limit_req_module
--without-mail_pop3_module --without-mail_smtp_module
--without-mail_imap_module --without-http_uwsgi_module
--without-http_scgi_module --without-http-cache


More information about the nginx mailing list