Running applications

All runtime components in the system are executed and managed as systemd services. Our applications have av- in their name therefore you can easily find them.

Each package is deployed as a dedicated service unit, ensuring consistent startup behavior, process supervision, and integration with the system lifecycle.

Service Management

• Services are automatically started on system boot.

• Each component runs independently under its own systemd unit.

• Restart policies are configured to ensure automatic recovery in case of failure for most apps.

• Service logs are available through journalctl for debugging and monitoring.

• Some services depend on others (e.g. mavlink-router, mediamtx) and may require those to be running before startup.

• Configuration changes typically require a service restart to take effect.

• In development or debugging scenarios, services can be stopped and the .sh script used by service can be run directly.