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)

diff --git a/source3/smbd/server.c b/source3/smbd/server.c
index 035469cd629621b2220f7299fa208e42202ebb3c..ed07e5c02b07a7935baba13102c9e62e22cb3edb 100644 (file)
--- 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;
 }