summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2009-03-26 12:24:50 +0100
committerKarolin Seeger <kseeger@samba.org>2009-03-27 13:06:56 +0100
commit1fc6fb588ac74c704bbdf98199fea74e08962da4 (patch)
tree481f33f7b64e9a7e06516b6197832c4441d5e505
parenta596eb3115464725ac2e8c897554d9b5c6a707f3 (diff)
downloadsamba-1fc6fb588ac74c704bbdf98199fea74e08962da4.tar.gz
samba-1fc6fb588ac74c704bbdf98199fea74e08962da4.tar.xz
samba-1fc6fb588ac74c704bbdf98199fea74e08962da4.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. (cherry picked from commit f73d4cf1fcfd8f9e2543a222faed133472fd890c)
-rw-r--r--source/locking/locking.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/source/locking/locking.c b/source/locking/locking.c
index eebf8701b50..b8cd29f8a60 100644
--- a/source/locking/locking.c
+++ b/source/locking/locking.c
@@ -854,7 +854,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;
}