1. 21 Jan, 2013 6 commits
    • 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.
    • JINMEI Tatuya's avatar
      [master] Merge branch 'trac2438' · c4df99ea
      JINMEI Tatuya authored
      resolved Conflicts:
    • Michal 'vorner' Vaner's avatar
    • Tomek Mrugalski's avatar
      [master] Merge branch 'trac2597' (server-id is now stored by dhcpv{4,6}) · 6167f31e
      Tomek Mrugalski authored
    • 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.
    • Naoki Kambe's avatar
      [master] Merge branch 'trac2225_statistics' · 0a89b374
      Naoki Kambe authored
  2. 18 Jan, 2013 13 commits
  3. 17 Jan, 2013 16 commits
  4. 16 Jan, 2013 5 commits