Skip to content
Snippets Groups Projects
  1. Nov 23, 2023
  2. Nov 21, 2023
  3. Nov 19, 2023
  4. Nov 17, 2023
  5. Nov 16, 2023
  6. Oct 06, 2023
  7. Apr 25, 2023
  8. Mar 07, 2023
    • Serguei Kolos's avatar
      Merge branch 'deps' into 'master' · 845c4b5f
      Serguei Kolos authored
      Add missing dependency
      
      See merge request atlas-tdaq-software/ipc!8
      ipc-05-14-16
      845c4b5f
    • Reiner Hauser's avatar
      Add missing dependency · 50dda3e2
      Reiner Hauser authored
      This only shows up on our biggest machines occasionally (48 cores)
      as:
      
      In file included from /builds/atlas-tdaq-software/tdaq-cmake/tdaq/tdaq-99-00-00/ipc/proxy/proxy.cc:13:
      /builds/atlas-tdaq-software/tdaq-cmake/tdaq/tdaq-99-00-00/ipc/ipc/proxy/proxy.h:13:10: fatal error: proxy/proxy.hh: No such file or directory
         13 | #include <proxy/proxy.hh>
            |          ^~~~~~~~~~~~~~~~
      compilation terminated.
      50dda3e2
  9. Feb 21, 2023
  10. Sep 15, 2022
  11. Sep 12, 2022
    • Reiner Hauser's avatar
      Allow to specify a custom endpoint to be published · 485508ce
      Reiner Hauser authored
      If the TDAQ_IPC_PUBLISH_ENDPOINT environment variable is set
      create an EndPointPublishPolicy with the specified address
      and pass it to the POA. The endpoint must be fully
      specified, including protocol, hostname and port number.
      
      Note this changes only the publishing, the ORB still chooses
      his own endpoint with the usual rules.
      
      For this to work some process has to listen at the specified
      address and then forward incoming connections to the original
      ORB (e.g. via an SSH tunnel).
      
      The use case is an ipc_gateway_proxy process on a system that
      allows outgoing connections but no incoming ones:
      
          export TDAQ_IPC_PUBLISH_ENDPOINT=giop:iiop:gatewayIP:8765
          ssh -f -N -R gatewayIP:8765:localIP:12346
          ipc_gateway_proxy -i privateIP -p 12345 -I proxyIP -P 12346
      
      All outgoing connections go through proxy, and the proxy connects
      directly to the remote hosts. Incoming connections are going
      to the gatewayIP:8765 host/port and are tunnelled back to
      the public part of the proxy, which in turn talks to the local
      hosts. This is possible since the ssh tunnel was established
      from inside the restricted network.
      
      The /etc/ssh/sshd_config host must have an entry:
      
          GatewayPorts clientspecified
      
      or the gateway host will only listen on the localhost interface.
      485508ce
  12. Apr 15, 2022
  13. Feb 14, 2022
  14. Jan 13, 2022
  15. Dec 02, 2021
  16. Nov 12, 2021
  17. Oct 21, 2021
  18. Sep 09, 2021
  19. Jul 09, 2021
  20. Mar 18, 2021
  21. Nov 27, 2020
  22. Nov 05, 2020
  23. Sep 25, 2020
  24. Sep 24, 2020
  25. Apr 13, 2020
  26. Feb 13, 2020
  27. Feb 12, 2020
  28. Feb 11, 2020
  29. Apr 17, 2019
Loading