From 6fd867f036b0dfbc4d6639c737467132b41dd2e5 Mon Sep 17 00:00:00 2001 From: Jeremy Allison Date: Thu, 15 Jan 2009 15:52:41 -0800 Subject: Allow reinit_after_fork to be called safely from within swat and other binaries that don't have an event context or a msg context. Fixes crash bug in swat. Jeremy. --- source3/lib/util.c | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/source3/lib/util.c b/source3/lib/util.c index 1e6ee56230..70eabbfa99 100644 --- a/source3/lib/util.c +++ b/source3/lib/util.c @@ -966,18 +966,22 @@ bool reinit_after_fork(struct messaging_context *msg_ctx, return false; } - /* - * For clustering, we need to re-init our ctdbd connection after the - * fork - */ - status = messaging_reinit(msg_ctx); - if (!NT_STATUS_IS_OK(status)) { - DEBUG(0,("messaging_reinit() failed: %s\n", - nt_errstr(status))); - return false; + if (msg_ctx) { + /* + * For clustering, we need to re-init our ctdbd connection after the + * fork + */ + status = messaging_reinit(msg_ctx); + if (!NT_STATUS_IS_OK(status)) { + DEBUG(0,("messaging_reinit() failed: %s\n", + nt_errstr(status))); + return false; + } } - event_context_reinit(ev_ctx); + if (ev_ctx) { + event_context_reinit(ev_ctx); + } return true; } -- cgit