OpenRC and systemd unit file interoperability in Artix Linux: Compatibility limits and conversion needs

Direct Answer

A native systemd unit file (.service) cannot be executed with full feature parity on Artix Linux OpenRC, even with systemd-compat installed. While the compatibility layer allows basic binaries to launch via ExecStart, it is a translation layer, not a full implementation of the systemd manager. If your service relies on advanced lifecycle management, complex dependencies, or specific systemd-only directives, it must be converted into a native OpenRC runscript.

Compatibility Limits

The systemd-compat layer focuses on basic execution. The following options are known to fail or behave inconsistently:

• Lifecycle Hooks: ExecStartPre and ExecStartPost are typically ignored. Any prerequisite setup must be handled within a native OpenRC start() function.
• Process Tracking: Type=notify is unsupported. OpenRC cannot process the notification sockets systemd uses to determine when a service is "ready."
• Environment & Logging: EnvironmentFile directives may be ignored, and logging directives intended for journald will not function as expected, as OpenRC typically logs to syslog or messages.

Dependency Resolution and Sequencing

Systemd uses a complex, parallelized dependency graph (Wants=, Requires=, After=). OpenRC uses a more linear, script-based dependency model. When using the compatibility layer, these complex graphs do not map 1:1. This often results in incorrect start-up sequencing or race conditions where a service attempts to start before its required network or filesystem dependencies are fully initialized.

Conversion Threshold

Conversion to a native OpenRC runscript is strongly recommended if the unit file meets any of the following criteria:

1. It uses any Type other than simple.
2. It requires ExecStartPre or ExecStartPost for initialization.
3. It has strict boot-ordering requirements that must be guaranteed.
4. It relies on systemd-specific features like Socket Activation or Timer units.

Verification Steps

To verify if a compat-unit is functioning correctly, use the following scoped commands:

# Check if the process actually launched
ps aux | grep [service_name]

# Verify the service status within OpenRC
rc-status

Missing Diagnostic Detail: To provide a more specific recommendation, please specify if the service in question requires a specific Type= (e.g., forking or notify) or relies on a specific After= target.