Blame SOURCES/network-Do-not-spam-journal-by-useless-warnings.patch

6237cd
From a7b0a65898ed10d109eaa10b34a9516c0c05f774 Mon Sep 17 00:00:00 2001
6237cd
From: Ondrej Holy <oholy@redhat.com>
6237cd
Date: Thu, 15 Dec 2016 11:18:00 +0100
6237cd
Subject: [PATCH] network: Do not spam journal by useless warnings
6237cd
6237cd
The following warning is always printed from network backend
6237cd
if smb backend is installed and network backend is mounted:
6237cd
Couldn't create directory monitor on smb://[WORKGROUP]/.
6237cd
6237cd
You can see it with two different error messages. The first is
6237cd
printed if we are not in samba environment, or the workgroup is
6237cd
misconfigured:
6237cd
Error: The specified location is not mounted
6237cd
6237cd
The second is printed in other cases, because monitoring is not
6237cd
supported by smb backend:
6237cd
Error: Operation not supported by backend
6237cd
6237cd
This isn't really useful and just spams the journal, let's use
6237cd
g_debug instead of g_warning.
6237cd
---
6237cd
 daemon/gvfsbackendnetwork.c | 2 +-
6237cd
 1 file changed, 1 insertion(+), 1 deletion(-)
6237cd
6237cd
diff --git a/daemon/gvfsbackendnetwork.c b/daemon/gvfsbackendnetwork.c
6237cd
index fc6cca47..95fee1d6 100644
6237cd
--- a/daemon/gvfsbackendnetwork.c
6237cd
+++ b/daemon/gvfsbackendnetwork.c
6237cd
@@ -358,7 +358,7 @@ recompute_files (GVfsBackendNetwork *backend)
6237cd
           else
6237cd
             {
6237cd
 	      char *uri = g_file_get_uri (server_file);
6237cd
-              g_warning ("Couldn't create directory monitor on %s. Error: %s", 
6237cd
+              g_debug ("Couldn't create directory monitor on %s. Error: %s",
6237cd
 	     		 uri, error->message);
6237cd
 	      g_free (uri);
6237cd
               g_clear_error (&error);
6237cd
-- 
6237cd
2.15.0
6237cd