summaryrefslogtreecommitdiff
path: root/source3
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2008-06-11 18:56:20 +0200
committerVolker Lendecke <vl@samba.org>2008-06-11 18:58:26 +0200
commit5b8259c11240417913cd4140f90ad70ee88316ed (patch)
treec8f3a121735a68d6be10354a9aa5f312f41e884a /source3
parent95a1f88d930808a7f1e63f47d78f349b4967b8a4 (diff)
downloadsamba-5b8259c11240417913cd4140f90ad70ee88316ed.tar.gz
samba-5b8259c11240417913cd4140f90ad70ee88316ed.tar.bz2
samba-5b8259c11240417913cd4140f90ad70ee88316ed.zip
Fix max_fd calculation in event_loop_once
For some bugs I really wonder how they can go undetected for so long. Fix a bug reported by Mathias Dietz. No samba bugzilla entry, but still 100% needed for 3-2-stable. Volker (cherry picked from commit 82c994dabc47bb4755c883a1f3651bb5d65cf2c5) (This used to be commit 91c73e093a03b10426b671cb3e1dffb8a2455d47)
Diffstat (limited to 'source3')
-rw-r--r--source3/lib/events.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/source3/lib/events.c b/source3/lib/events.c
index 8134a7ac1c..7750176d8e 100644
--- a/source3/lib/events.c
+++ b/source3/lib/events.c
@@ -344,7 +344,7 @@ int event_loop_once(struct event_context *ev)
return 0;
}
- ret = sys_select(maxfd, &r_fds, &w_fds, NULL, &to);
+ ret = sys_select(maxfd+1, &r_fds, &w_fds, NULL, &to);
if (ret == -1 && errno != EINTR) {
return -1;