s3: Use sys_write in fork_domain_child

Counterpart for last checkin. A lot less likely, but not impossible in a child.

Autobuild-User: Volker Lendecke <vlendec@samba.org>
Autobuild-Date: Fri Aug 26 13:14:27 CEST 2011 on sn-devel-104
(cherry picked from commit e0e3d215b1902ecbeb3d469af9a196856711921e)

diff --git a/source3/winbindd/winbindd_dual.c b/source3/winbindd/winbindd_dual.c
index 0b4cc6ef6e60fd04b20901bd43e2a67d3446d787..99dbdcf245ae4d1026a74b3916a53ce489c8e094 100644 (file)
--- a/source3/winbindd/winbindd_dual.c
+++ b/source3/winbindd/winbindd_dual.c
@@ -1361,7 +1361,7 @@ static bool fork_domain_child(struct winbindd_child *child)
 
        status = winbindd_reinit_after_fork(child, child->logfilename);
 
-       nwritten = write(state.sock, &status, sizeof(status));
+       nwritten = sys_write(state.sock, &status, sizeof(status));
        if (nwritten != sizeof(status)) {
                DEBUG(1, ("fork_domain_child: Could not write status: "
                          "nwritten=%d, error=%s\n", (int)nwritten,