LEARN. PRACTICE. GROW.Concept and mechanism
In systemd, enabled and active answer different questions. Enable configures future activation through the unit rather than necessarily starting the process immediately. Start acts on current state, and enable --now combines intentions when appropriate. To investigate failure, inspect state and unit logs during the relevant interval. Journalctl filters by service and time, reducing mixed events. Retain evidence before restarting when possible. A service can exist and be stopped without its package being absent. Changed configuration may also require reload or restart according to the application contract; editing a file does not necessarily change the running process immediately.
Guided application
Capacity requires observing the right resource. Df shows filesystem usage; du helps locate directory consumption. A filesystem can have free blocks and exhausted inodes, preventing new files. In a fictional batch, millions of old temporary files justify investigating retention and ownership before bounded cleanup. Deleting everything in /var can destroy other services’ data. For Permission denied, inspect more than the final file: the process needs search permission on path directories. Confirm user, groups, and applicable additional controls. Intervention should address the observed cause and prevent recurrence through measures such as temporary-file lifecycle and capacity alerts with assigned ownership.
Enabled and inactive can coexist without contradiction.
Common pitfalls
Restart before evidence; free blocks as unlimited capacity; file chmod without path analysis.
Related topics: Linux, shell, and permissions · Networking and recovery · Cloud, responsibility, and cost
Choose observations that distinguish hypotheses before changing the system.
Reference: systemctl service lifecycle · LFCA domains and competencies updated2025-09-16; current page confirmed2026-09-30