From 10f0c785c70b89e76f3a9cd3b319262affc9447e Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Thu, 30 Sep 2010 16:27:42 +0200 Subject: s3: Re-introduce a procid_self() Giving the parent pid to reinit_after_fork is not a good idea.... None of the other callers do this, checked it. --- source3/winbindd/winbindd_dual.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'source3/winbindd') diff --git a/source3/winbindd/winbindd_dual.c b/source3/winbindd/winbindd_dual.c index 4cec7c2a1a..931ec6787a 100644 --- a/source3/winbindd/winbindd_dual.c +++ b/source3/winbindd/winbindd_dual.c @@ -1133,7 +1133,7 @@ bool winbindd_reinit_after_fork(const char *logfilename) status = reinit_after_fork( winbind_messaging_context(), winbind_event_context(), - messaging_server_id(winbind_messaging_context()), + procid_self(), true); if (!NT_STATUS_IS_OK(status)) { DEBUG(0,("reinit_after_fork() failed\n")); -- cgit