diff options
author | Carlos Garnacho <carlosg@gnome.org> | 2017-10-18 23:29:26 +0200 |
---|---|---|
committer | Carlos Garnacho <carlosg@gnome.org> | 2017-11-14 22:45:26 +0100 |
commit | 5a318139d53a7e87ccc36c9db4ab586143aec1ca (patch) | |
tree | 6f087b6edf2773d11c2b903d57fb61c45d194890 | |
parent | b2c67b93a175631f8252277d0f6b981d879ba662 (diff) | |
download | tracker-5a318139d53a7e87ccc36c9db4ab586143aec1ca.tar.gz |
libtracker-miner: Disable monitoring when dealing with unknown monitors
We just can't do safe assumptions about its limits or behavior, seems
best to turn monitoring off altogether.
-rw-r--r-- | src/libtracker-miner/tracker-monitor.c | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/src/libtracker-miner/tracker-monitor.c b/src/libtracker-miner/tracker-monitor.c index fdd6c0265..991248cd7 100644 --- a/src/libtracker-miner/tracker-monitor.c +++ b/src/libtracker-miner/tracker-monitor.c @@ -299,12 +299,9 @@ tracker_monitor_init (TrackerMonitor *object) } else { /* Unknown */ - g_warning ("Monitor backend:'%s' is unknown, we have no limits " - "in place because we don't know what we are dealing with!", + g_warning ("Monitor backend:'%s' is unhandled. Monitoring will be disabled", name); - - /* Guessing limit... */ - priv->monitor_limit = 100; + priv->enabled = FALSE; } g_file_monitor_cancel (monitor); @@ -312,7 +309,9 @@ tracker_monitor_init (TrackerMonitor *object) } g_object_unref (file); - g_debug ("Monitor limit is %d", priv->monitor_limit); + + if (priv->enabled) + g_debug ("Monitor limit is %d", priv->monitor_limit); } static void |