[nginx] Events: made a failure to create a notification channel ...

Maxim Dounin mdounin at mdounin.ru
Mon Jan 25 19:42:55 UTC 2016

details:   http://hg.nginx.org/nginx/rev/67422a0a8ed2
branches:  stable-1.8
changeset: 6339:67422a0a8ed2
user:      Ruslan Ermilov <ru at nginx.com>
date:      Wed May 06 17:04:00 2015 +0300
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.


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

diffs (12 lines):

diff --git a/src/event/modules/ngx_epoll_module.c b/src/event/modules/ngx_epoll_module.c
--- a/src/event/modules/ngx_epoll_module.c
+++ b/src/event/modules/ngx_epoll_module.c
@@ -329,7 +329,7 @@ ngx_epoll_init(ngx_cycle_t *cycle, ngx_m
         if (ngx_epoll_notify_init(cycle->log) != NGX_OK) {
-            return NGX_ERROR;
+            ngx_epoll_module_ctx.actions.notify = NULL;

More information about the nginx-devel mailing list