[tracker] libtracker-miner: Don't disable monitoring during crawling

[Martyn James Russell <mr src gnome org>]

commit 76279f5a304ccdf2ead3880577ffd8bd5fb6b8bb
Author: Martyn Russell <martyn lanedo com>
Date:   Tue Sep 8 16:34:28 2009 +0100

    libtracker-miner: Don't disable monitoring during crawling
    
    This meant that no monitors were getting added even though the log
    said the opposite, this was because we added a NULL pointer to the
    hash table for each GFile.

 src/libtracker-miner/tracker-miner-fs.c |    7 -------
 1 files changed, 0 insertions(+), 7 deletions(-)
---
diff --git a/src/libtracker-miner/tracker-miner-fs.c b/src/libtracker-miner/tracker-miner-fs.c
index b5d9238..e9ce966 100644
--- a/src/libtracker-miner/tracker-miner-fs.c
+++ b/src/libtracker-miner/tracker-miner-fs.c
@@ -249,9 +249,6 @@ tracker_miner_fs_init (TrackerMinerFS *object)
 	/* Set up the monitor */
 	priv->monitor = tracker_monitor_new ();
 
-	g_message ("Disabling monitor events until we have crawled the file system");
-	tracker_monitor_set_enabled (priv->monitor, FALSE);
-
 	g_signal_connect (priv->monitor, "item-created",
 			  G_CALLBACK (monitor_item_created_cb),
 			  object);
@@ -1403,14 +1400,10 @@ crawl_directories_stop (TrackerMinerFS *fs)
 		tracker_crawler_stop (fs->private->crawler);
 	}
 
-	g_message ("Enabling monitor events");
-	tracker_monitor_set_enabled (fs->private->monitor, TRUE);
-	
 	/* Is this the right time to emit FINISHED? What about
 	 * monitor events left to handle? Should they matter
 	 * here?
 	 */
-
 	if (fs->private->crawl_directories_id != 0) {
 		g_source_remove (fs->private->crawl_directories_id);
 		fs->private->crawl_directories_id = 0;