1. 20 Oct, 2017 2 commits
  2. 02 Oct, 2017 3 commits
  3. 14 Sep, 2017 2 commits
  4. 11 Sep, 2017 1 commit
  5. 07 Sep, 2017 3 commits
  6. 31 Aug, 2017 3 commits
  7. 30 Aug, 2017 2 commits
  8. 28 Aug, 2017 5 commits
  9. 27 Aug, 2017 1 commit
  10. 26 Aug, 2017 2 commits
    • Michael Terry's avatar
      monitor: limit memory usage of deja-dup-monitor · 37cb14ef
      Michael Terry authored
      We've had reports of deja-dup-monitor taking all the system memory.
      But I haven't been able to reproduce. In an attempt to prevent the
      monitor from dragging down the system, set a limit on memory use
      by the autostart monitor process using ulimit.
      
      This needs continued watching to see if we can fix this for real.
      And to make sure we haven't made anything worse with this
      workaround.
      
      (Also in this commit, we rename the file and move it in-source.)
      
      https://launchpad.net/bugs/1302416
      37cb14ef
    • Michael Terry's avatar
      Fix settings being marked read-only when started via --restore · 8d98914c
      Michael Terry authored
      We used to keep a global read-only setting if we were doing a restore.
      But now with dbus-activation and one central process, that didn't make
      any sense. And we could stick the whole process in read-only settings
      mode if we were started with with --restore.
      
      Instead of a global settings table, we now have ConfigLocation generate
      a Backend object that gets passed down to the Operation objects.
      Likewise we are careful in various places to use the same Settings
      objects.
      8d98914c
  11. 25 Aug, 2017 2 commits
  12. 24 Aug, 2017 4 commits
  13. 22 Aug, 2017 5 commits
  14. 21 Aug, 2017 1 commit
  15. 20 Aug, 2017 2 commits
  16. 19 Aug, 2017 2 commits