Provided there is a process manager running at some-host:1234. That can be done on some-host via:
drunc-process-manager ssh-standalone 1234
Alternatively, the process manager's port can be dynamic (0), and in that case the command drunc-process-manager will print out which port it is expecting traffic from (and the unified shell can connect to it in the same way).
Of course, the usual command is still valid to start your own process manager:
Enable the Process manager to run as a daemon, and the unified shell to connect to it. The target for this is v5.3.0. This fixes https://github.com/DUNE-DAQ/drunc/issues/212
With this PR, the unified shell can be started with
Provided there is a process manager running at
some-host:1234. That can be done onsome-hostvia:Alternatively, the process manager's port can be dynamic (0), and in that case the command
drunc-process-managerwill print out which port it is expecting traffic from (and the unified shell can connect to it in the same way).Of course, the usual command is still valid to start your own process manager: