From 8b6d41b3b083dd5876e8fbfdce4afed191b8da0f Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Mon, 23 Jun 2008 17:32:32 +0200 Subject: smbd: don't panic if messaging_init() fails but return NULL leaving panic or more appropriate action to callers. This can for instance happen in a clustered setup, when ctdb is not running. This allows for a more defined behaviour, reducing chicken-egg-problems. Michael (This used to be commit 3b6541ff483d5fea4fd30bb6a01a560c05028d4e) --- source3/smbd/server.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source3/smbd/server.c b/source3/smbd/server.c index 035469cd62..ed07e5c02b 100644 --- a/source3/smbd/server.c +++ b/source3/smbd/server.c @@ -92,7 +92,7 @@ struct messaging_context *smbd_messaging_context(void) if (!ctx && !(ctx = messaging_init(NULL, server_id_self(), smbd_event_context()))) { - smb_panic("Could not init smbd messaging context"); + DEBUG(0, ("Could not init smbd messaging context.\n")); } return ctx; } -- cgit