s3:smbd: change a loglevel from 0 to 1 when SMB_VFS_CONNECT fails

Logging at level 0 may result in log flooding. Additionally log the
share name that failed in SMB_VFS_CONNECT.

Signed-off-by: Ralph Boehme <slow@samba.org>
Reviewed-by: Volker Lendecke <vl@samba.org>
Autobuild-User(master): Ralph Böhme <slow@samba.org>
Autobuild-Date(master): Thu Jul 16 20:24:47 CEST 2015 on sn-devel-104

diff --git a/source3/smbd/service.c b/source3/smbd/service.c
index 05449672fb740fa7a5ab2ce98e0662950f2a5b0e..ba8946d5d2fab82d66b7cf8642989b8734ea3416 100644 (file)
--- a/source3/smbd/service.c
+++ b/source3/smbd/service.c
@@ -669,7 +669,9 @@ static NTSTATUS make_connection_snum(struct smbXsrv_connection *xconn,
 
        if (SMB_VFS_CONNECT(conn, lp_servicename(talloc_tos(), snum),
                            conn->session_info->unix_info->unix_name) < 0) {
-               DEBUG(0,("make_connection: VFS make connection failed!\n"));
+               DBG_WARNING("SMB_VFS_CONNECT for service '%s' at '%s' failed: %s\n",
+                           lp_servicename(talloc_tos(), snum), conn->connectpath,
+                           strerror(errno));
                status = NT_STATUS_UNSUCCESSFUL;
                goto err_root_exit;
        }