1. 30 Jan, 2013 3 commits
    • Jeremy C. Reed's avatar
      [master] DHCP4_SERVERID_LOADED and DHCP6_SERVERID_LOADED need server-id too · 937c982c
      Jeremy C. Reed authored
      On my home system I received error when running unit tests like:
      Message DHCP4_SERVERID_LOADED server-id /home/reed/opt/bind10/var/b10-dhcp4-serverid has been loaded from file %2
      assertion ""Excess logger placeholders still exist in message" == NULL" failed: file "../../../../src/lib/log/log_formatter.cc", line 69, function "void isc::log::checkExcessPlaceholders(std::string*, unsigned int)"
      I am using --enable-logger-checks. The build farm also uses that.
      I am not sure why this was not seen  on the build farm.
      I added the missing value for dhcp4 and dhcp6 and the make check completed.
      It had slight review on jabber.
    • Shane Kerr's avatar
      Typo fixes. · e6348b61
      Shane Kerr authored
    • Michal 'vorner' Vaner's avatar
      Rename log message ID · 5351989c
      Michal 'vorner' Vaner authored
      Logging XFRIN_TRANSFER_PROTOCOL_ERROR as INFO level message could be
      confusing. Rename to XFRIN_TRANSFER_PROTOCOL_VIOLATION, which is
      neutral which has a neutral name regarding the log levels.
  2. 29 Jan, 2013 1 commit
  3. 28 Jan, 2013 3 commits
  4. 27 Jan, 2013 1 commit
  5. 24 Jan, 2013 8 commits
  6. 23 Jan, 2013 7 commits
  7. 22 Jan, 2013 13 commits
  8. 21 Jan, 2013 4 commits
    • Stephen Morris's avatar
      [2559] Remove spurious commas in DHCP .spec files · 6c6f4051
      Stephen Morris authored
      Also correct error messages in the configuration parser: the
      same error is logged on any parser error, both creation and
      running.  The text was made more general.
    • Shane Kerr's avatar
      [2608] Kill msgq if we cannot connect to it on startup · 016925ef
      Shane Kerr authored
      When the boss process was unable to connect to the msgq, it would
      exit. However, it would leave the msgq process running. This patch
      fixes that by killing the msgq if it is running in this case.
    • Marcin Siodelski's avatar
    • Michal 'vorner' Vaner's avatar
      Fix stats tests after merge of #2582 · 32973fce
      Michal 'vorner' Vaner authored
      The problem was, msgq started to open more file descriptors than before.
      Also, the changes meant the tests didn't shut down their internal copy
      of msgq properly, leaking more file descriptors.
      * Do the shutdown correctly.
      * Wait for msgq to terminate, so there are no race conditions between
        the old (shutting down one) and a new one for another test.
      * Close all the data sockets in msgq, to prevent further leaks. The
        other ends probably still leak, but at least the threads on the other
        ends terminate on EOF, so we don't leak the threads too.
      * Wait for the other threads too, so we don't spawn too many threads.
      * Unrelated cleanup: remove unneeded output-suppression workaround from
        the tests, it is no longer needed.
      * Unrelated cleanup: Initialize testing logger for the tests. But it
        still logs for no apparent reason, needs to be examined.