Improvements for SCDAQ control by function manager

Hi,

In the following a wishlist with features that would make interaction with SCDAQ easier for the FM. For context, the FM currently

• copies one (or, in the future maybe more) configuration file to the host
• restarts the runSCdaq service

It would probably be useful if we could maintain the ability to run SCDAQ as a service (but if there are strong reasons against it, we can look at options to operate it differently). It would also be useful if we could have one configuration file instead of N_streams files, for e.g. the calo system I would imagine that something of the following form would make sense from my perspective:

{
    "output_filename_prefix": "scout_CALO",
    "output_filename_base": "/fff/ramdisk/",
    "processor_type": "CALO", 
    "comment": "I'm unsure if processor type isn't a per-stream setting...",
    ...
    "input_streams": [
        {
             "primitive_type": "JET",
             "source_id": 22,
             "tcp_dest_port": 10010
        },
        {
             "primitive_type": "EGAMME",
             "source_id": 23,
             "tcp_dest_port": 10011
        }
    ]
}

I see that we currently have a output_filename_suffix field, which is set to e.g. .raw_1. If it's possible, I think that it would be nicer to have this set once (not per stream) and then add the _x suffix automatically based on the number of input streams SCDAQ is handling.

Cheers, Dinyar