From cb7c54230a00215c30d9ea5b0cdfb0837d3ee47d Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Thu, 26 Mar 2009 12:24:50 +0100 Subject: [PATCH] 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 74efc72bca5707ff35df9282c843d62c4cf331c3) --- source/locking/locking.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/locking/locking.c b/source/locking/locking.c index 9bd53614f71..41fe1c96cc4 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; } -- 2.11.4.GIT