... | @@ -30,7 +30,7 @@ Here are the suite of template services for a single front end model: |
... | @@ -30,7 +30,7 @@ Here are the suite of template services for a single front end model: |
|
|
|
|
|
The `rts@target` is the primary unit to interact with. If you want to start the `h1lsc` model you would execute:
|
|
The `rts@target` is the primary unit to interact with. If you want to start the `h1lsc` model you would execute:
|
|
```shell
|
|
```shell
|
|
# systemctl start rts@h1lsc.target
|
|
$ sudo systemctl start rts@h1lsc.target
|
|
```
|
|
```
|
|
That would then start the `rts-module@h1lsc.service` to load the kernel module, the `rts-epics@h1lsc.service` to start the EPICS IOC process, and the `rts-awgtpman@h1lsc.service` to start the awgtpman process.
|
|
That would then start the `rts-module@h1lsc.service` to load the kernel module, the `rts-epics@h1lsc.service` to start the EPICS IOC process, and the `rts-awgtpman@h1lsc.service` to start the awgtpman process.
|
|
|
|
|
... | @@ -47,20 +47,20 @@ The DAQD components are managed directly with systemd via `systemctl`. Here are |
... | @@ -47,20 +47,20 @@ The DAQD components are managed directly with systemd via `systemctl`. Here are |
|
|
|
|
|
The services are controlled via `systemctl`:
|
|
The services are controlled via `systemctl`:
|
|
```shell
|
|
```shell
|
|
# systemctl enable rts-daqd.service
|
|
$ sudo systemctl enable rts-daqd.service
|
|
# systemctl start rts-daqd.service
|
|
$ sudo systemctl start rts-daqd.service
|
|
# systemctl stop rts-daqd.service
|
|
$ sudo systemctl stop rts-daqd.service
|
|
```
|
|
```
|
|
|
|
|
|
### distributed front ends
|
|
### distributed front ends
|
|
|
|
|
|
The various distributed front end transport mechanisms (available in separate `advligorts-transport-*` packages) also include service units. The same package holds both the 'xmit' and 'recv' services and would be installed on both the front end and the data concentrator. On the front end, to enable and start the 'cps' transport sender:
|
|
The various distributed front end transport mechanisms (available in separate `advligorts-transport-*` packages) also include service units. The same package holds both the 'xmit' and 'recv' services and would be installed on both the front end and the data concentrator. On the front end, to enable and start the 'cps' transport sender:
|
|
```shell
|
|
```shell
|
|
# systemctl enable --now rts-cps_xmit.service
|
|
$ sudo systemctl enable --now rts-cps_xmit.service
|
|
```
|
|
```
|
|
On the data concentrator run:
|
|
On the data concentrator run:
|
|
```shell
|
|
```shell
|
|
# systemctl enable --now rts-cps_recv.service
|
|
$ sudo systemctl enable --now rts-cps_recv.service
|
|
```
|
|
```
|
|
|
|
|
|
## config for systemd services
|
|
## config for systemd services
|
... | @@ -73,7 +73,7 @@ If for some reason you need to customize a systemd unit, the best way is to use |
... | @@ -73,7 +73,7 @@ If for some reason you need to customize a systemd unit, the best way is to use |
|
|
|
|
|
Systemd provides a nice interface to do this using the `systemctl edit` command. To edit unit `unit.service`, run the following command:
|
|
Systemd provides a nice interface to do this using the `systemctl edit` command. To edit unit `unit.service`, run the following command:
|
|
```shell
|
|
```shell
|
|
# systemctl edit unit.serice
|
|
$ sudo systemctl edit unit.serice
|
|
```
|
|
```
|
|
This will create a "drop-in" override in:
|
|
This will create a "drop-in" override in:
|
|
```
|
|
```
|
... | @@ -84,7 +84,7 @@ To completely replace a unit file use `systemctl edit --full`, which creates a r |
... | @@ -84,7 +84,7 @@ To completely replace a unit file use `systemctl edit --full`, which creates a r |
|
|
|
|
|
If you've made changes manually, reload systemd:
|
|
If you've made changes manually, reload systemd:
|
|
```shell
|
|
```shell
|
|
# systemctl daemon-reload
|
|
$ sudo systemctl daemon-reload
|
|
```
|
|
```
|
|
|
|
|
|
## viewing logs
|
|
## viewing logs
|
... | | ... | |