summaryrefslogtreecommitdiff
path: root/source3/modules
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2009-04-28 11:16:19 +0200
committerVolker Lendecke <vl@samba.org>2009-04-28 11:21:49 +0200
commitc33291d49f888a7a29a07bc1735cbd890a23cb10 (patch)
treea39adde4bae4f7ae339fa24e40aa16fdfe7db41e /source3/modules
parentdd33abf649f4e1479365a2ccc2b41134270ff4ac (diff)
downloadsamba-c33291d49f888a7a29a07bc1735cbd890a23cb10.tar.gz
samba-c33291d49f888a7a29a07bc1735cbd890a23cb10.tar.bz2
samba-c33291d49f888a7a29a07bc1735cbd890a23cb10.zip
Fix annoying debug messages when no snapshots are used
Not being able to open the shadow copy directory is the same as having no shadow copy support at all. The VFS module should in this case not log with debug level 0 and set ENOSYS to indicate "no shadow copies used" to the higher levels.
Diffstat (limited to 'source3/modules')
-rw-r--r--source3/modules/vfs_shadow_copy2.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/source3/modules/vfs_shadow_copy2.c b/source3/modules/vfs_shadow_copy2.c
index 9eaf8ee851..9543af32b9 100644
--- a/source3/modules/vfs_shadow_copy2.c
+++ b/source3/modules/vfs_shadow_copy2.c
@@ -513,9 +513,10 @@ static int shadow_copy2_get_shadow_copy2_data(vfs_handle_struct *handle,
p = SMB_VFS_NEXT_OPENDIR(handle, snapdir, NULL, 0);
if (!p) {
- DEBUG(0,("shadow_copy2: SMB_VFS_NEXT_OPENDIR() failed for '%s' - %s\n",
- snapdir, strerror(errno)));
+ DEBUG(2,("shadow_copy2: SMB_VFS_NEXT_OPENDIR() failed for '%s'"
+ " - %s\n", snapdir, strerror(errno)));
talloc_free(tmp_ctx);
+ errno = ENOSYS;
return -1;
}