> You may be able to fix this by setting `error_log` yourself in your
http configuration section.
Check the config I provided, error_log is defined there. Yet the warning
is printed, because nginx tries to access error_log before reading
config file. I can start nginx (with a warning) after
@Thomas, this is a bug report, not a request to change paths or
anything. I believe it should be reported upstream and tracked here.
Nginx should NOT ignore prefix provided on command line with -p switch
regardless of paths provided at compile time.
--
You received this bug notification because
You may be able to fix this by setting `error_log` yourself in your http
configuration section.
Anything that's precompiled with a prefix will need **manually
overridden** in your nginx.conf file. Either way, this isn't a problem
with the packaging, this is a problem with your configuraiton
NGINX Upstream has similar pre3fixes set in their prebuilt packages as
well:
--error-log-path=/var/log/nginx/error.log --http-log-
path=/var/log/nginx/access.log --pid-path=/var/run/nginx.pid --lock-
path=/var/run/nginx.lock --http-client-body-temp-
path=/var/cache/nginx/client_temp
@Thomas - I lack the context knowledge, can you speak to these issues?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899164
Title:
nginx ignores prefix path
To manage notifications about this bug
paelzer: These are paths chosen by Upstream Debian - we aren't going to
alter those compile time paths.
Marking Won't Fix. (If you need an NGINX that works with nonstandard
paths, you should probably be compiling NGINX yourself)
** Changed in: nginx (Ubuntu)
Status: New => Won't Fix
--
