s3: Use sys_read in fork_domain_child
commit7228ed0429d39d1cd153a1c29d38cd0f9532e623
authorVolker Lendecke <vl@samba.org>
Fri, 26 Aug 2011 09:38:21 +0000 (26 11:38 +0200)
committerKarolin Seeger <kseeger@samba.org>
Fri, 16 Sep 2011 18:42:30 +0000 (16 20:42 +0200)
tree99c5bb4dad7be5f5e0a344b690e03d8b043b3e0a
parente6b3258e3b2691140425175d41cc73c6e0647b1f
s3: Use sys_read in fork_domain_child

I've seen

[2011/08/26 01:44:10.872057,  1] winbindd/winbindd_dual.c:1336(fork_domain_child)
  fork_domain_child: Could not read child status: nread=-1, error=Interrupted system call

on a customer box. Not good.
(cherry picked from commit 964e809ce2069ad888e0fb12dfe51bac5a461508)

The last 3 patches address bug #8409 (f7d97868 created a new race condition).
(cherry picked from commit 2f0a5b477f58378c3505631d15b422057b037efe)
source3/winbindd/winbindd_dual.c