systemctl daemon-reload vs restart: what each command changes
Daemon-reload makes the manager reread unit definitions, while restart stops and starts a unit using the definition currently loaded after any reload.
Pass secrets with systemd credentials instead of environment variables
Systemd credentials make selected data available to a service through a protected runtime path and can support encrypted credentials depending on system capabilities.
Set systemd service environment variables without hidden drift
A service receives the environment assembled by its unit and manager, not the interactive shell that launched systemctl.
Use network-online.target without hiding application retries
Network-online.target is a boot synchronization point supplied by a network manager; it does not prove a particular DNS name, route, or dependency is usable.
Set systemd CPU and memory limits with observable headroom
Systemd applies resource controls to the unit cgroup, so MemoryMax, CPUQuota, TasksMax, and weights affect the whole supervised process tree.
Choose a systemd Restart policy without creating a crash loop
Restart decides which exit causes trigger another start, while RestartSec and start limits control retry pacing and containment.
Use systemd socket activation without two processes fighting for a port
A socket unit owns the listening descriptor and passes accepted or listening sockets to an activated service according to the service protocol.
systemd timer vs cron: choose by scheduling and observability needs
A timer activates another unit and records state in systemd, while cron launches commands from a separate scheduler and environment.
Run a systemd user service and understand login persistence
A user manager owns per-user units; login sessions, lingering, environment, and system units are separate lifecycles.
Fix a systemd WorkingDirectory failure with an explicit path
WorkingDirectory changes the process current directory before ExecStart and can fail startup when the path or permissions are wrong.