summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2009-03-26 12:24:50 +0100
committerVolker Lendecke <vl@samba.org>2009-03-26 12:30:44 +0100
commitc164c0c20ac0420878a9f7aba6503d3deb8e53d5 (patch)
tree51f53a1b30b782f8d08b917caec47f547b7a2359
parent7eb7f423d048e869a19d560ab0d1ba3b51b62fa9 (diff)
downloadsamba-c164c0c20ac0420878a9f7aba6503d3deb8e53d5.tar.gz
samba-c164c0c20ac0420878a9f7aba6503d3deb8e53d5.tar.bz2
samba-c164c0c20ac0420878a9f7aba6503d3deb8e53d5.zip
Fix a scary "fill_share_mode_lock failed" message
To me "fill_share_mode_lock failed" is a "can't happen" alert. There is however a perfectly valid case in get_file_infos() when the file is not open. Change the corresponding debug message to level 10 and explain more.
-rw-r--r--source3/locking/locking.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/source3/locking/locking.c b/source3/locking/locking.c
index bafb89522a..70841225a7 100644
--- a/source3/locking/locking.c
+++ b/source3/locking/locking.c
@@ -887,7 +887,8 @@ struct share_mode_lock *fetch_share_mode_unlocked(TALLOC_CTX *mem_ctx,
}
if (!fill_share_mode_lock(lck, id, servicepath, fname, data, NULL)) {
- DEBUG(3, ("fill_share_mode_lock failed\n"));
+ DEBUG(10, ("fetch_share_mode_unlocked: no share_mode record "
+ "around (file not open)\n"));
TALLOC_FREE(lck);
return NULL;
}