details: http://hg.nginx.org/nginx/rev/d0a84ae2fb48
branches:
changeset: 6144:d0a84ae2fb48
user: Ruslan Ermilov <ru@nginx.com>
date: Wed May 06 17:04:00 2015 +0300
description:
Events: made a failure to create a notification channel non-fatal.

This may happen if eventfd() returns ENOSYS, notably seen on CentOS 5.4.
Such a failure will now just disable the notification mechanism and let
the callers cope with it, instead of failing to start worker processes.
If thread pools are not configured, this can safely be ignored.

diffstat:

src/event/modules/ngx_epoll_module.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diffs (12 lines):

diff -r 162b2d27d4e1 -r d0a84ae2fb48 src/event/modules/ngx_epoll_module.c
--- a/src/event/modules/ngx_epoll_module.c Wed Apr 29 14:59:02 2015 +0300
+++ b/src/event/modules/ngx_epoll_module.c Wed May 06 17:04:00 2015 +0300
@@ -329,7 +329,7 @@ ngx_epoll_init(ngx_cycle_t *cycle, ngx_m

#if (NGX_HAVE_EVENTFD)
if (ngx_epoll_notify_init(cycle->log) != NGX_OK) {
- return NGX_ERROR;
+ ngx_epoll_module_ctx.actions.notify = NULL;
}
#endif


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