- Nov 23, 2023
-
-
Serguei Kolos authored
-
- Nov 21, 2023
-
-
Serguei Kolos authored
-
- Nov 19, 2023
-
-
Serguei Kolos authored
-
Serguei Kolos authored
-
- Nov 17, 2023
-
-
Serguei Kolos authored
-
Serguei Kolos authored
-
Serguei Kolos authored
-
- Nov 16, 2023
-
-
Serguei Kolos authored
-
Serguei Kolos authored
-
Serguei Kolos authored
-
- Oct 06, 2023
-
-
Serguei Kolos authored
-
- Apr 25, 2023
-
-
Serguei Kolos authored
-
- Mar 07, 2023
-
-
Serguei Kolos authored
Add missing dependency See merge request atlas-tdaq-software/ipc!8
-
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.
-
- Feb 21, 2023
-
-
Serguei Kolos authored
-
- Sep 15, 2022
-
-
Serguei Kolos authored
Revert "Merge branch 'publish' into 'master'" See merge request atlas-tdaq-software/ipc!7
-
Serguei Kolos authored
This reverts merge request !6
-
Serguei Kolos authored
Allow to specify a custom endpoint to be published See merge request atlas-tdaq-software/ipc!6
-
- Sep 12, 2022
-
-
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.
-
- Apr 15, 2022
-
-
Serguei Kolos authored
-
- Feb 14, 2022
-
-
Serguei Kolos authored
-
- Jan 13, 2022
-
-
Serguei Kolos authored
SSL support for CORBA See merge request atlas-tdaq-software/ipc!4
-
-
- Dec 02, 2021
-
-
Serguei Kolos authored
-
- Nov 12, 2021
-
-
Serguei Kolos authored
-
- Oct 21, 2021
-
-
Serguei Kolos authored
-
- Sep 09, 2021
-
-
Serguei Kolos authored
-
- Jul 09, 2021
-
-
Serguei Kolos authored
-
- Mar 18, 2021
-
-
Serguei Kolos authored
-
- Nov 27, 2020
-
-
Serguei Kolos authored
-
Serguei Kolos authored
-
- Nov 05, 2020
-
-
Serguei Kolos authored
-
- Sep 25, 2020
-
-
Serguei Kolos authored
Apache 2.0 license See merge request atlas-tdaq-software/ipc!3
-
- Sep 24, 2020
-
-
Reiner Hauser authored
-
- Apr 13, 2020
-
-
Serguei Kolos authored
-
Serguei Kolos authored
-
- Feb 13, 2020
-
-
Serguei Kolos authored
-
- Feb 12, 2020
-
-
Serguei Kolos authored
Use the CMake C compiler to preprocess file. See merge request atlas-tdaq-software/ipc!2
-
- Feb 11, 2020
-
-
Reiner Hauser authored
This makes sure it finds the executable even in cross-compilation mode where search paths are different.
-
- Apr 17, 2019
-
-
Serguei Kolos authored
-