Automatic start by using systemd - Revision history

Uwe: /* Configuration of automatic start */

2026-02-17T17:50:42Z

Configuration of automatic start

← Older revision		Revision as of 19:50, 17 February 2026
Line 46:		Line 46:

	For starting the control application manually via systemd, one can use the command <code>sudo systemctl start aquarium_control_startup.sh</code>.		For starting the control application manually via systemd, one can use the command <code>sudo systemctl start aquarium_control_startup.sh</code>.

			Note: Waiting for the NTP before starting the application will avoid a wrong timestamp occurring, but may inhibit the start of the application if the internet connectivity is gone.

	== Creating message queues for operation or test of aquarium_control ==		== Creating message queues for operation or test of aquarium_control ==

2026-02-17T17:49:34Z

Configuration of automatic start

← Older revision		Revision as of 19:49, 17 February 2026
Line 27:		Line 27:
	After=multi-user.target		After=multi-user.target

	~~## wait for ntp to get updated time~~
	After=network-online.target time-sync.target		After=network-online.target time-sync.target
	Wants=network-online.target time-sync.target		Wants=network-online.target time-sync.target

2026-02-17T17:49:25Z

Configuration of automatic start

← Older revision		Revision as of 19:49, 17 February 2026
Line 27:		Line 27:
	After=multi-user.target		After=multi-user.target

	\# wait for ntp to get updated time		## wait for ntp to get updated time
	After=network-online.target time-sync.target		After=network-online.target time-sync.target
	Wants=network-online.target time-sync.target		Wants=network-online.target time-sync.target

2026-02-17T17:49:18Z

Configuration of automatic start

← Older revision		Revision as of 19:49, 17 February 2026
Line 27:		Line 27:
	After=multi-user.target		After=multi-user.target

	# wait for ntp to get updated time		\# wait for ntp to get updated time
	After=network-online.target time-sync.target		After=network-online.target time-sync.target
	Wants=network-online.target time-sync.target		Wants=network-online.target time-sync.target

2026-02-17T17:49:00Z

Configuration of automatic start

← Older revision		Revision as of 19:49, 17 February 2026
Line 27:		Line 27:
	After=multi-user.target		After=multi-user.target

			# wait for ntp to get updated time
			After=network-online.target time-sync.target
			Wants=network-online.target time-sync.target

	[Service]		[Service]
Line 44:		Line 47:

	For starting the control application manually via systemd, one can use the command <code>sudo systemctl start aquarium_control_startup.sh</code>.		For starting the control application manually via systemd, one can use the command <code>sudo systemctl start aquarium_control_startup.sh</code>.


	== Creating message queues for operation or test of aquarium_control ==		== Creating message queues for operation or test of aquarium_control ==

2026-01-01T10:26:46Z

start the application to run in the background

← Older revision		Revision as of 12:26, 1 January 2026
Line 86:		Line 86:
	The lock file has to be initialised to contain zero upon restart of the server. A missing or empty lock file is interpreted by the control application that something has gone wrong and startup will be aborted. In case of uncontrolled shutdown (e.g. power failure), the PID of the last operation may still be in the lock file, hence a reset to zero is required for this case.		The lock file has to be initialised to contain zero upon restart of the server. A missing or empty lock file is interpreted by the control application that something has gone wrong and startup will be aborted. In case of uncontrolled shutdown (e.g. power failure), the PID of the last operation may still be in the lock file, hence a reset to zero is required for this case.

	== ~~start~~ the application to run in the background ==		== Start the application to run in the background ==
			The start of the application in the background is triggered with the following command:
	<code>		<code>
	/usr/local/bin/aquarium_control > /dev/null&		/usr/local/bin/aquarium_control > /dev/null&
	</code>		</code>

2026-01-01T10:26:19Z

initialize lock file with zero as PID

← Older revision		Revision as of 12:26, 1 January 2026
Line 77:		Line 77:
	Only one of the message queues is required for operating the control application. The other message queues are use for parallel SW unit testing.		Only one of the message queues is required for operating the control application. The other message queues are use for parallel SW unit testing.

	== ~~initialize~~ lock file with zero as PID ==		== Initialize lock file with zero as PID ==
			The startup script contains the following command:

	<code>		<code>
	sudo echo 0 > /var/local/aquarium-ctrl.pid		sudo echo 0 > /var/local/aquarium-ctrl.pid
	</code>		</code>

	The lock file has to be initialised to zero upon restart of the server. A missing or empty lock file is interpreted by the control application that something has gone wrong and startup will be aborted. In case of uncontrolled shutdown (e.g. power failure), the PID of the last operation may still be in the lock file, hence a reset to zero is required for this case.		The lock file has to be initialised to contain zero upon restart of the server. A missing or empty lock file is interpreted by the control application that something has gone wrong and startup will be aborted. In case of uncontrolled shutdown (e.g. power failure), the PID of the last operation may still be in the lock file, hence a reset to zero is required for this case.

	== start the application to run in the background ==		== start the application to run in the background ==

2026-01-01T10:25:31Z

← Older revision		Revision as of 12:25, 1 January 2026
Line 1:		Line 1:
			== Content of the startup script ==
	The shell script for startup of the control application (<code>/usr/local/bin/aquarium_control_startup</code>) has the following content:		The shell script for startup of the control application (<code>/usr/local/bin/aquarium_control_startup</code>) has the following content:

Line 16:		Line 17:
	Finally, it starts the control application in the background.		Finally, it starts the control application in the background.

			== Configuration of automatic start ==
	The content of systemd unit file <code>/lib/systemd/system/aquarium_control.service</code> as following:		The content of systemd unit file <code>/lib/systemd/system/aquarium_control.service</code> as following:

2026-01-01T10:24:16Z

Creating message queues for operation or test of aquarium_control

← Older revision		Revision as of 12:24, 1 January 2026
Line 45:		Line 45:

	== Creating message queues for operation or test of aquarium_control ==		== Creating message queues for operation or test of aquarium_control ==
			The startup script contains the creation of a set of message queues:

	<code>		<code>
	sudo touch /dev/mqueue/aquarium_control.5UXp		sudo touch /dev/mqueue/aquarium_control.5UXp

2026-01-01T10:23:40Z

← Older revision		Revision as of 12:23, 1 January 2026
Line 4:		Line 4:
	echo 0 > /var/local/aquarium-ctrl.pid		echo 0 > /var/local/aquarium-ctrl.pid

	touch /dev/mqueue/aquarium_control.6UXp		sudo touch /dev/mqueue/aquarium_control.6UXp

	chmod o+rwx /dev/mqueue/aquarium_control.6UXp		chmod o+rwx /dev/mqueue/aquarium_control.6UXp