osmo-bts/contrib/systemd/osmo-bts-trx.service

[Unit]
Description=Osmocom osmo-bts for osmo-trx

[Service]
Type=simple
ExecStart=/usr/bin/osmo-bts-trx -s -c /etc/osmocom/osmo-bts-trx.cfg
StateDirectory=osmocom
WorkingDirectory=%S/osmocom
Restart=always
RestartSec=2

# Let it process messages quickly enough
CPUSchedulingPolicy=rr
CPUSchedulingPriority=1

[Install]
WantedBy=multi-user.target
Move systemd service to contrib/systemd Move it there and have only a symlink in debian/, like we do in all other projects. Change-Id: I213d3816a66e88069c31f85b3fbf462d1222aa43 2018-09-06 10:32:16 +00:00			`[Unit]`
			`Description=Osmocom osmo-bts for osmo-trx`

			`[Service]`
			`Type=simple`
Install sample cfg file to /etc/osmocom Change cfg file names so they don't overlap when installing different osmo-bts versions, and make systemd services look for correct new name. Remove unneeded duplicated EXTRA_DIST files from root dir Makefile.am Change-Id: I75fdd06cc52ce50628efb1f9b007d2e3926db27d 2018-09-12 17:06:33 +00:00			`ExecStart=/usr/bin/osmo-bts-trx -s -c /etc/osmocom/osmo-bts-trx.cfg`
Set working directory in systemd service file By default systemd will execute service with root directory (or home directory for user instance) which might result in attempts to create files in unexpected place. Let's set it to 'osmocom' subdir of state directory (/var/lib for system instance) instead. Related: OS#4821 Change-Id: I4b7bcd441e5da81c4c5267715675041171a1ce1e 2022-09-09 13:46:33 +00:00			`StateDirectory=osmocom`
			`WorkingDirectory=%S/osmocom`
Move systemd service to contrib/systemd Move it there and have only a symlink in debian/, like we do in all other projects. Change-Id: I213d3816a66e88069c31f85b3fbf462d1222aa43 2018-09-06 10:32:16 +00:00			`Restart=always`
			`RestartSec=2`

			`# Let it process messages quickly enough`
			`CPUSchedulingPolicy=rr`
			`CPUSchedulingPriority=1`

			`[Install]`
			`WantedBy=multi-user.target`