| commit | 59021d00c9f719755343a268e074cb153ce3d985 | |
| author | Volker Lendecke <vl@samba.org> | |
| Wed, 7 Oct 2009 13:53:46 +0000 (7 15:53 +0200) | ||
| committer | Karolin Seeger <kseeger@samba.org> | |
| Thu, 8 Oct 2009 12:50:05 +0000 (8 14:50 +0200) | ||
| tree | aab8cb7e96169a81935b52fc1b1d8a7e6b9add08 | treesnapshot (tar.gz zip) |
| parent | f35684bf980ab397468ae194302e65a42928273e | 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 a4df4406f12281db60fd6612c6ebf93d77af9152)
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 a4df4406f12281db60fd6612c6ebf93d77af9152)
| source/winbindd/winbindd.c | diffblobblamehistory |