summaryrefslogtreecommitdiff
path: root/daemon/gvfsbackendnetwork.c
diff options
context:
space:
mode:
authorOndrej Holy <oholy@redhat.com>2016-12-15 11:18:00 +0100
committerOndrej Holy <oholy@redhat.com>2016-12-15 11:50:10 +0100
commita7b0a65898ed10d109eaa10b34a9516c0c05f774 (patch)
tree9871a61c108fd2f31659815c151c62f665af00cd /daemon/gvfsbackendnetwork.c
parent4c6bac455bd099735a818837c06da663fc0da921 (diff)
downloadgvfs-a7b0a65898ed10d109eaa10b34a9516c0c05f774.tar.gz
network: Do not spam journal by useless warnings
The following warning is always printed from network backend if smb backend is installed and network backend is mounted: Couldn't create directory monitor on smb://[WORKGROUP]/. You can see it with two different error messages. The first is printed if we are not in samba environment, or the workgroup is misconfigured: Error: The specified location is not mounted The second is printed in other cases, because monitoring is not supported by smb backend: Error: Operation not supported by backend This isn't really useful and just spams the journal, let's use g_debug instead of g_warning.
Diffstat (limited to 'daemon/gvfsbackendnetwork.c')
-rw-r--r--daemon/gvfsbackendnetwork.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/daemon/gvfsbackendnetwork.c b/daemon/gvfsbackendnetwork.c
index fc6cca47..95fee1d6 100644
--- a/daemon/gvfsbackendnetwork.c
+++ b/daemon/gvfsbackendnetwork.c
@@ -358,7 +358,7 @@ recompute_files (GVfsBackendNetwork *backend)
else
{
char *uri = g_file_get_uri (server_file);
- g_warning ("Couldn't create directory monitor on %s. Error: %s",
+ g_debug ("Couldn't create directory monitor on %s. Error: %s",
uri, error->message);
g_free (uri);
g_clear_error (&error);