service-management

To configure systemd to automatically restart a crashed service, you create a unit file with correct restart policies and dependency wiring. This ensures your services recover from failures automatically across reboots without requiring manual babysitting or intervention.

Debugging a systemd service startup failure involves analyzing journald logs and systemctl status. This Skill guides you through operational debugging by using journalctl, checking resource or port conflicts, and reproducing the issue manually as the service user to isolate the root cause.

Preventing journald logs from filling the disk requires configuring log rotation and lifecycle management. This Skill helps you set up journald and logrotate configurations so operational logs are maintained properly without consuming all available system storage over time.

Yes, you can use systemd watchdog integration for health checks on your production service. This Skill assists in implementing health check strategies using either HTTP health endpoints or systemd watchdog integration to detect and handle silently degrading services.

The best way to harden a systemd unit file is by applying least-privilege principles and safe filesystem or environment handling. This Skill helps you create reliable unit files with security hardening, proper startup ordering, and safe environment configurations for production.