1. 23 Oct, 2021 2 commits
  2. 22 Mar, 2021 1 commit
  3. 22 Oct, 2020 2 commits
  4. 25 Sep, 2020 1 commit
  5. 21 Sep, 2020 1 commit
  6. 15 Sep, 2020 1 commit
  7. 30 Aug, 2020 2 commits
  8. 24 Aug, 2020 1 commit
    • Sam Thursfield's avatar
      Log a g_message() on startup · 30fa0b21
      Sam Thursfield authored
      The Tracker daemons used to be very verbose. We cleaned a lot of this up
      behind TRACKER_DEBUG= but we went too far. I now find myself wondering
      if logging to the journal is working. This commit guarantees that we
      output at least one log message on startup to confirm that logging is
      working.
      30fa0b21
  9. 19 Aug, 2020 2 commits
  10. 01 Aug, 2020 3 commits
  11. 05 Jul, 2020 1 commit
    • Carlos Garnacho's avatar
      tracker-miner-fs: Preempt graph creation · 08a5cc5b
      Carlos Garnacho authored
      This is a busy operation that we can squeeze in the initial delay,
      or along the startup phase if there was no delay. In initial indexing
      graph creation is a significant chunk of indexing time, so it's
      something we can prepare in advance.
      
      The graph creation operation is still not that *much* I/O heavy, so
      it's unlikely that it'd influence session startup negatively.
      08a5cc5b
  12. 04 Jul, 2020 2 commits
  13. 03 Jul, 2020 1 commit
  14. 18 Jun, 2020 2 commits
  15. 06 Jun, 2020 1 commit
  16. 21 May, 2020 1 commit
    • Carlos Garnacho's avatar
      tracker-miner-fs: Drop tracker-writeback interaction · 3a0aa24a
      Carlos Garnacho authored
      There was this code still taking care of listening to tracker-store
      changes, and doing the PerformWriteback call. The former was gone
      and this got broken. Now tracker-writeback has replacement API, so
      this no longer is necessary.
      3a0aa24a
  17. 03 May, 2020 1 commit
  18. 01 May, 2020 2 commits
    • Carlos Garnacho's avatar
      tracker-miner-fs: Change usage of graphs · 10417012
      Carlos Garnacho authored
      Both tracker-miner-fs and tracker-extract will use TrackerModuleManager
      infrastructure to find the graph where a file's nie:InformationElement
      belongs to. All data from tracker-extract will be dumped in the same
      graph.
      
      For nie:DataObjects, and supporting nie:InformationElements created for
      files that do not have an extractor (eg. nfo:Folder), we will use the
      tracker:FileSystem graph.
      
      This makes all filesystem data in tracker:FileSystem, and all extracted
      metadata in the other graphs, as specified by extract modules.
      10417012
    • Sam Thursfield's avatar
      miners/fs: Log when we exit on domain shutdown · 5c4ab090
      Sam Thursfield authored
      Otherwise, the 'Shutdown started' message appears with no explanation
      as to why tracker-miner-fs chose now to shutdown.
      5c4ab090
  19. 27 Apr, 2020 1 commit
  20. 20 Apr, 2020 2 commits
    • Sam Thursfield's avatar
      Remove TRACKER_VERBOSITY and tracker-log module · e5692b9f
      Sam Thursfield authored
      Users should now use G_MESSAGES_DEBUG=Tracker to see debug messages
      on the console.
      
      The TRACKER_VERBOSITY only worked if tracker_log_init() had been called,
      which can't be done when libtracker-sparql is being used from an
      application outside of Tracker.
      
      This also removes some little-used config utilities in the cli.
      For `tracker reset --config`, you can instead use `gsettings
      --reset-recursively`.
      e5692b9f
    • Sam Thursfield's avatar
      Remove obsolete sched-idle config option · 0eb0cb10
      Sam Thursfield authored
      We already don't honour this option, we always request SCHED_IDLE
      priority regardless.
      0eb0cb10
  21. 06 Apr, 2020 6 commits
  22. 08 Mar, 2020 1 commit
  23. 06 Mar, 2020 1 commit
  24. 17 Feb, 2020 2 commits