| commit | 4e458a6b46c20ed61695df2c8fc765139d021419 | |
| author | Volker Lendecke <vl@samba.org> | |
| Wed, 7 Oct 2009 12:06:53 +0000 (7 14:06 +0200) | ||
| committer | Karolin Seeger <kseeger@samba.org> | |
| Tue, 20 Oct 2009 13:00:26 +0000 (20 15:00 +0200) | ||
| tree | 19b69b446318dad1aeadf58f06faf88e0cb6d51a | treesnapshot (tar.gz zip) |
| parent | ede45f4fab7768fb0838d1546d0b78e4abc2ea34 | commitdiff |
s3:winbind: Only ever handle one event after a select call
While handling an fd event, the situation with other fds can change. I've just
seen a winbind stuck in the accept() call on the privileged pipe. I can only
imagine this happen because under high load we first handled other requests and
meanwhile the client on the privileged pipe went away.
(cherry picked from commit 8ef4a183da8bdc9997c198678a931b111396c104)
While handling an fd event, the situation with other fds can change. I've just
seen a winbind stuck in the accept() call on the privileged pipe. I can only
imagine this happen because under high load we first handled other requests and
meanwhile the client on the privileged pipe went away.
(cherry picked from commit 8ef4a183da8bdc9997c198678a931b111396c104)
| source3/winbindd/winbindd.c | diffblobblamehistory |