1. 26 Jun, 2011 2 commits
  2. 20 Jun, 2011 1 commit
  3. 16 Jun, 2011 1 commit
    • Jelte Jansen's avatar
      [trac1010] add logger config update call · 384501f8
      Jelte Jansen authored
      Renamed the original my_logconfig_handler() to default_logconfig_handler and made it public. This is now called by the python wrapper function log_config_update (a module function in isc.log)
      384501f8
  4. 07 Jun, 2011 1 commit
  5. 03 Jun, 2011 2 commits
  6. 25 May, 2011 5 commits
  7. 24 May, 2011 1 commit
  8. 20 May, 2011 2 commits
  9. 19 May, 2011 1 commit
    • JINMEI Tatuya's avatar
      [trac931] Fix double reads · 67d9442a
      JINMEI Tatuya authored
      It was possible to schedule two reads of message length at once. That
      actually read two 4-bytes chunks, one from the beginning of the real
      message.
      67d9442a
  10. 16 May, 2011 2 commits
  11. 13 May, 2011 2 commits
  12. 11 May, 2011 2 commits
    • Jelte Jansen's avatar
      [trac743] update a doxy message · f5278f2a
      Jelte Jansen authored
      f5278f2a
    • Jelte Jansen's avatar
      [trac743] Replace direct output by liblog calls · c47f23e5
      Jelte Jansen authored
      While creating messages and extended descriptions, I noticed a few potential problems, which I also fixed;
      
      - If the config manager does not accept the modules specification, or if the
        'get current config' command returns with an error, the system used to
        ignore that fact apart from printing an error, and continue running. It
        seems much better to explicitely fail, since the module would be running
        independent of what its config is supposed to be, which would be really
        unstable
      - If the module cannot parse a command it gets over the command channel,
        it used to send back an error. If we have multiple modules listening on
        the same channel, this would result in multiple errors being returned
        It will now log an error, but it will not send back an answer
      c47f23e5
  13. 21 Jan, 2011 1 commit
  14. 11 Jan, 2011 1 commit
  15. 10 Jan, 2011 1 commit
  16. 07 Jan, 2011 3 commits
  17. 03 Jan, 2011 1 commit
  18. 17 Oct, 2010 1 commit
  19. 16 Aug, 2010 1 commit
  20. 06 Aug, 2010 1 commit
  21. 09 Jul, 2010 1 commit
  22. 08 Jul, 2010 2 commits
  23. 02 Jul, 2010 1 commit
  24. 01 Jul, 2010 1 commit
  25. 20 May, 2010 2 commits
  26. 18 Mar, 2010 1 commit