1. 04 Jul, 2017 2 commits
  2. 03 Jul, 2017 2 commits
  3. 22 Jun, 2017 1 commit
  4. 12 Apr, 2017 1 commit
  5. 29 Mar, 2017 1 commit
  6. 03 Jan, 2017 2 commits
  7. 22 Dec, 2016 1 commit
    • Thomas Markwalder's avatar
      [5046] CommandMgr dups the connection socket prior to executing command · e5a6c2b4
      Thomas Markwalder authored
      src/lib/config/command_mgr.cc
          CommandMgr::commandReader(int sockfd) - duplicates the connection
          socket to use for repsonding in case the command closes the channel.
      
      src/lib/testutils/io_utils.cc
          fileExists() - now uses stat() function so one can use it on any
          type of file, like a unix socket
      
      updated unit tests accordingly
      e5a6c2b4
  8. 16 Dec, 2015 2 commits
  9. 22 Jun, 2015 1 commit
  10. 17 Jun, 2015 2 commits
  11. 16 Jun, 2015 2 commits
    • Tomek Mrugalski's avatar
      [3880] Changes after review: · 0bbcd619
      Tomek Mrugalski authored
       - log messages in commandReader are now errors, not warnings
       - missing doxygen comment added
      0bbcd619
    • Tomek Mrugalski's avatar
      [3880] Changes after review: · c0f65ef8
      Tomek Mrugalski authored
       - Extra logging messages for socket failures
       - strerror() is now reported when encountering low-level errors
       - fcntl, accept return codes are now verified
       - minor tweaks in CtrlDhcpv4SrvTest.command* unit-tests.
      c0f65ef8
  12. 13 Jun, 2015 1 commit
  13. 10 Jun, 2015 1 commit
  14. 22 Jul, 2014 1 commit
  15. 22 Feb, 2013 1 commit
  16. 03 Feb, 2012 1 commit
  17. 01 Feb, 2012 1 commit
    • Jelte Jansen's avatar
      [640] send around 'stopping' messages, and handle them · 4e8a4299
      Jelte Jansen authored
      When closing a ModuleCCSession, a 'i am stopping' message is now sent to the ConfigManager, which in turn informs Cmdctl (which then causes bindctl to update its list).
      
      This causes stopped modules to disappear from bindctl until such time that they are enabled or started again, so that config updates and most importantly, commands, do not cause weird timeouts (bindctl will immediately inform you of modules not running)
      4e8a4299
  18. 22 Jul, 2011 1 commit
  19. 15 Jul, 2011 1 commit
  20. 24 Jun, 2011 3 commits
  21. 07 Jun, 2011 1 commit
  22. 12 May, 2011 1 commit
  23. 11 May, 2011 1 commit
    • 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
  24. 10 May, 2011 1 commit
  25. 19 Jan, 2011 1 commit
  26. 05 Jan, 2011 1 commit
  27. 16 Oct, 2009 1 commit