Run a systemd user service and understand login persistence

For systemd user service, the safest approach is a bounded operational change, not a command pasted without context. This runbook starts with effective state, shows the smallest candidate action, and finishes by repeating the real user or system path.

TL;DR: A user manager owns per-user units; login sessions, lingering, environment, and system units are separate lifecycles. Capture a baseline with systemctl --user status, make the reviewed change only when the evidence matches, then verify with systemctl --user is-enabled example.service and keep the rollback ready.

Audience: Linux operators who can read a unit file and have sudo access plus a second recovery session. This guide assumes familiarity with systemd and a change window appropriate to the system.

The direct answer

The unit runs under the intended user manager and survives only the lifecycle explicitly configured. That is the success condition for systemd user service; command completion by itself is not enough.

The important boundary is unit definition, manager state, process state, and dependency ordering. A user manager owns per-user units; login sessions, lingering, environment, and system units are separate lifecycles. If an observation does not identify which side of that boundary failed, collect a narrower observation before changing state.

How the mechanism works

For systemd user service, use this mental model: systemd first loads unit configuration, calculates a dependency transaction, creates a cgroup, then supervises the processes associated with that unit. The model prevents a common mistake—treating configuration text, control-plane acceptance, process state, and end-user behavior as the same proof.

Follow four stages:

1. Observe: identify the exact host, object, version, owner, and active configuration.
2. Interpret: write the expected result, the abnormal result, and what would remain inconclusive.
3. Change: apply one reviewed action at the narrowest layer that contradicts the baseline.
4. Verify: repeat the original path and compare the same evidence, including adjacent safety controls.

Preflight and safety boundary

Keep the current service process and a second shell available until syntax, effective properties, and the real request path have all been verified.

Before systemd user service, record UTC time, the current version or digest, the exact target, recent changes, and who owns the workload. The rollback for this runbook is: disable the user unit, revert lingering only if this change enabled it, and verify no orphaned process remains.

Do not continue if the target identity is ambiguous, the current state cannot be saved, the only recovery session would be at risk, or the proposed command affects more objects than the brief names.

Capture the read-only baseline

Run these commands one at a time. Replace example names and addresses deliberately; do not paste production secrets into a transcript.

systemctl --user status
systemctl --user cat example.service
loginctl show-user \"$USER\" -p Linger -p State

Interpret the baseline before moving on:

• Expected: the unit runs under the intended user manager and survives only the lifecycle explicitly configured.
• Abnormal: the command works in a login shell but the user manager lacks the environment or ends after logout.
• Inconclusive: missing output can also mean the wrong context, permissions, namespace, log window, binary, or target. Prove those assumptions before treating absence as health.

Save the decisive output, exit status, and timestamp. Redact credentials, customer data, private topology, tokens, and complete environment dumps.

Apply the smallest candidate change

The following is state-changing example syntax, not an instruction to run it unchanged:

systemctl --user enable --now example.service

For systemd user service, the proposed change is acceptable only when the read-only baseline predicts its effect and the rollback is available. The key risk is: enabling lingering keeps a user manager active without a login and expands the lifetime of every enabled user unit.

Prefer an immutable artifact, validated configuration, dry-run, transaction, candidate object, or staged target when the tool supports one. Record the exact command and UTC time so later telemetry can be correlated to the change.

Verify the result from the outside in

systemctl --user is-enabled example.service
systemctl --user is-active example.service
journalctl --user-unit example.service --since today --no-pager

Verification for systemd user service has three layers:

1. The control plane or command reports the intended effective state.
2. The process, resource, or data path reflects that state without a new pressure signal.
3. The original user-visible or dependent-system path succeeds from an independent vantage point.

If systemctl --user is-enabled example.service succeeds but the original path still fails, stop. The change may have repaired a local symptom while DNS, policy, routing, caching, dependency, or client state remains broken.

Failure branches

The baseline does not match this runbook

When the command works in a login shell but the user manager lacks the environment or ends after logout, do not force the candidate command. Return to identity and scope, compare a healthy peer only through effective settings, and name a new falsifiable mechanism.

The change succeeds but behavior does not

A successful systemctl --user enable --now example.service proves that one interface accepted a request. It does not prove convergence, readiness, data compatibility, external routing, or client recovery. Re-run the same evidence at each downstream boundary.

The change makes the system worse

Execute the written rollback: disable the user unit, revert lingering only if this change enabled it, and verify no orphaned process remains. Preserve the failed candidate and relevant logs long enough to explain the outcome; do not destroy the evidence with broad cleanup or repeated restarts.

Operator checklist

• Confirm the exact target, context, identity, version, and active owner.
• Capture the read-only baseline and one disconfirming observation.
• Label systemctl --user enable --now example.service as state-changing during review.
• Keep recovery access and rollback independent of the path being edited.
• Change one layer, record UTC time, and wait for its real convergence boundary.
• Verify the original path, adjacent controls, resource pressure, and persistence.
• Update the runbook when observed behavior differs from the source-reviewed model.

Investigate it in Tryssh

$ systemctl --user is-enabled example.service
Expected: the unit runs under the intended user manager and survives only the lifecycle explicitly configured.

Tryssh can preserve this evidence loop and show a state-changing command for human approval. It does not make the operator's identity, recovery access, rollback, or platform authority decisions.

Evidence and review status

This systemd user service runbook was source-reviewed on 2026-07-29 against current first-party documentation. The commands are illustrative and use example targets. The page does not claim that the change was reproduced across every distribution, managed service, version, network, or workload.

Limitations and trade-offs

Enabling lingering keeps a user manager active without a login and expands the lifetime of every enabled user unit. Managed platforms may generate configuration, restrict privileges, replace local state, or expose a different control plane than the upstream project. Confirm the installed version and provider contract before applying a repair.

Search visibility is not proof of operational correctness. Treat this page as a decision aid, preserve independent recovery, and stop when the evidence contradicts its assumptions.

Related operator runbooks

Continue with systemd network-online.target, systemd timer vs cron, the systemd foundation guide, and the SSH hardening checklist.

Sources and further reading

• Systemd user service first-party reference
• systemctl manual
• systemd unit manual
• systemd execution environment manual