Make per-user systemd services survive logout and start at boot for reliable background tasks. 31.01.2026 | reading time: 2 min On servers and developer machines he sometimes needs timers, sockets or long-running agents tied to a user to keep running even when nobody is logged in; enabling lingering with `loginctl enable-linger username` makes the per-user systemd manager persistent and able to start at boot. What happens in practice Try this as root: `sudo loginctl enable-linger alice`; then confirm with `ls /var/lib/systemd/linger` which will list `alice`, and inspect `loginctl show-user alice` which will include `Linger=yes`; with lingering enabled a user-level service in `~/.config/systemd/user` can be started by the systemd user manager and will keep running after logout. When to use and what to watch Enable lingering for service accounts, scheduled jobs or persistent user sockets, but beware: lingering starts a user manager at boot which increases footprint and expands attack surface; check disk and memory impact, control which users have lingering, and remember to use `loginctl disable-linger username` to revert when no longer needed. Commands you will use often Useful commands include `loginctl enable-linger username`, `loginctl disable-linger username` and checking `/var/lib/systemd/linger`; to manage units remember `systemctl --user` for the per-user manager and inspect logs with `journalctl --user` when troubleshooting. Final thought Lingering is a small setting that changes when user services live; use it deliberately to run timers, socket-activated agents or per-user daemons reliably, then explore how this fits into overall systemd administration and best practices for security and resource control; consider advancing your skills with focused Linux certification prep at bitsandbytes.academy like CompTIA Linux+ or LPIC-1. Join Bits & Bytes Academy First class LINUX exam preparation. boot-process processes utilities security
