s3:smbd: slightly improve no sockets panic message

Signed-off-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
Reviewed-by: Jennifer Sutton <jennifersutton@catalyst.net.nz>

diff --git a/source3/smbd/server.c b/source3/smbd/server.c
index f31ea894600719f7a2cb7ea2be8e65a177b9307e..b3b50c72fa4c9f51e1fe5a4c27e7b13b954c1e54 100644 (file)
--- a/source3/smbd/server.c
+++ b/source3/smbd/server.c
@@ -2552,8 +2552,11 @@ quic_disabled:
                smbd_init_addrchange(NULL, ev_ctx, msg_ctx, parent);
        }
 
-       if (!open_sockets_smbd(parent, ev_ctx, msg_ctx))
-               exit_server("open_sockets_smbd() failed");
+       if (!open_sockets_smbd(parent, ev_ctx, msg_ctx)) {
+               DBG_ERR("smbd could not bind to a socket, which can be caused "
+                       "by a bad 'interfaces' line in smb.conf\n");
+               exit_server("Could not bind to any sockets\n");
+       }
 
        TALLOC_FREE(frame);
        /* make sure we always have a valid stackframe */