|
|
|
Back
Midas
Rome
Roody
Rootana
|
| Midas DAQ System |
Not logged in |
 |
|
19 Nov 2025, Stefan Mathis, Forum, Control external process from inside MIDAS
|
19 Nov 2025, Nick Hastings, Forum, Control external process from inside MIDAS
|
20 Nov 2025, Stefan Mathis, Forum, Control external process from inside MIDAS
|
20 Nov 2025, Nick Hastings, Forum, Control external process from inside MIDAS
|
20 Nov 2025, Stefan Mathis, Forum, Control external process from inside MIDAS
|
24 Nov 2025, Stefan Ritt, Forum, Control external process from inside MIDAS
|
27 Nov 2025, Konstantin Olchanski, Forum, Control external process from inside MIDAS
|
|
|
Message ID: 3121
Entry time: 19 Nov 2025
In reply to: 3120
Reply to this: 3122
|
| Author: |
Nick Hastings |
| Topic: |
Forum |
| Subject: |
Control external process from inside MIDAS |
|
|
Hi,
what you describe is exactly how I normally run mhttpd, mlogger, mserver and some other
custom frontend programs. Eg:
[local:T2KGSC:Running]/>ls /programs/Logger/
Required y
Watchdog timeout 100000
Check interval 180000
Start command systemctl --user start mlogger
Auto start n
Auto stop n
Auto restart n
Alarm class AlarmNotify
First failed 0
The only exception is your last point about stdout and stderr
being midas messages. I use journalctl to see these.
Cheers,
Nick.
> I want to control (start / stop / monitor its stdout and stderr) an external process (systemd / EPICS IOC shell script) from within MIDAS.
>
> In order to make this as convenient as possible for the user, I want the process to behave just like any other MIDAS client:
> - I can start it from the ODB as a program
> - The process gets regularly polled from MIDAS to see whether it is still running
> - I can stop the process from the ODB like any other program
> - Optional, but highly appreciated: Its stdout and stderr should be a MIDAS message.
>
> Did anyone already solve a similar problem?
>
> Best regards
> Stefan |