Check the systemd tutorial for more info.
| service | location | user |
|---|---|---|
| antmc | antservice | ubuntu |
| corr | corr01-16 | ubuntu |
| search | corr17-20 | ubuntu |
| T2 | corr00 | ubuntu |
| injection | corr00 | ubuntu |
| voltage | corr01-16 | ubuntu |
| trigger_copy | dsa-storage | user |
| send_cands | dsa-storage | user |
| calibration_preprocessing | dsa-storage | user |
| calibration | dsa-storage | user |
| bfcopy | dsa-storage | user |
| bokeh | bokehservice | ubuntu |
| hiplot | dsa-storage | user |
| dask-scheduler | h23 | user |
| dask-worker | h23 | user |
| statusmon | h23 | user |
| dashboard | h23 | user |
To ensure the service is started after networking is up(nice for those services connecting to etcd), add the following under the [Unit] declaration:
After=network-online.target
systemctl --user enable <service>
systemctl --user start <service>
journalctl --user-unit <service>