1. 12 Feb, 2008 1 commit
  2. 09 Feb, 2008 1 commit
  3. 06 Dec, 2007 1 commit
  4. 26 Nov, 2007 1 commit
  5. 08 Nov, 2007 1 commit
  6. 26 Sep, 2007 1 commit
  7. 01 Sep, 2007 1 commit
  8. 17 Aug, 2007 1 commit
  9. 11 Aug, 2007 2 commits
  10. 07 Aug, 2007 1 commit
  11. 06 Aug, 2007 1 commit
  12. 03 Aug, 2007 1 commit
  13. 25 Jul, 2007 1 commit
  14. 23 Jul, 2007 1 commit
  15. 21 Jul, 2007 2 commits
  16. 24 Feb, 2007 1 commit
  17. 09 Feb, 2007 3 commits
  18. 25 Jan, 2007 1 commit
  19. 04 Jan, 2007 5 commits
  20. 03 Jan, 2007 1 commit
  21. 02 Jan, 2007 1 commit
  22. 01 Jan, 2007 1 commit
  23. 31 Dec, 2006 1 commit
  24. 25 Sep, 2006 1 commit
  25. 14 Sep, 2006 1 commit
  26. 13 Sep, 2006 1 commit
  27. 12 Sep, 2006 2 commits
  28. 09 Sep, 2006 1 commit
  29. 06 Sep, 2006 2 commits
    • Pierangelo Masarati's avatar
      cleanup monitoring resources · 1fc5e8e0
      Pierangelo Masarati authored
      1fc5e8e0
    • Pierangelo Masarati's avatar
      - setup framework for monitoring of back-bdb/back-hdb stuff in their · 55f24ce8
      Pierangelo Masarati authored
        database entry in cn=monitor
      - improve support for custom attribute/callback registration
        in back-monitor
      - design API for registered antry/attr/callback removal in back-monitor
      
      HEADS UP: now back-bdb requires back-monitor to be present, either static
      or dynamically loaded __before__ back-bdb/back-hdb is initialized.
      This works for sure if both back-bdb & back-monitor are static or dynamic
      (provided back-monitor.la is loaded before back_bdb.la); it is not clear
      what happens if back-bdb is static and back-monitor is dynamic.  In case,
      either make back-bdb monitoring conditional, or hardwire back-monitor
      much like back-config and back-ldif.
      55f24ce8
  30. 29 Aug, 2006 1 commit