systemd

Manage EOS systemd service units, timers, and journald logs on Linux.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/antonyfmunoz/OS --skill systemd-antonyfmunoz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systemd
Source: https://github.com/antonyfmunoz/OS/tree/main/skills/tools/systemd
Command: npx skills add https://github.com/antonyfmunoz/OS --skill systemd-antonyfmunoz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of managing EOS services on a Linux VPS in a reliable, observable, and maintainable way using systemd instead of ad-hoc process handling and fragile cron patterns.

Core Features & Use Cases

  • Service lifecycle mastery: start/stop/restart/reload, enable/disable at boot, masking, and recovering from start-limit crash loops.
  • EOS service patterns: manage the four canonical EOS services (os-discord, os-bot, os-monitor, os-webhook) with consistent unit structure and journald logging.
  • Timers, journald, and overrides: replace cron with dependency-aware timers (including Persistent=true), query logs safely with journalctl, and layer configuration using drop-in overrides for secrets and resource caps.

Quick Start

Ask the AI how to create or debug the unit file for os-discord, then follow its guidance to validate the unit and inspect failures using systemctl and journalctl.

Frequently Asked Questions about systemd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a systemd unit file for an EOS service on Linux?

Replace cron with systemd timers by configuring dependency-aware scheduling and setting Persistent=true. This ensures missed runs execute later and manages service dependencies more reliably than ad-hoc cron patterns.

How do I debug systemd service failures using journald?

Debug systemd service failures by querying journald logs safely with journalctl to inspect errors. This approach provides observability for EOS services without needing to write application logs to external files.

Can I apply environment variables and resource limits to systemd services without editing the main unit file?

Apply environment variables and resource limits to systemd services by safely layering drop-in override files. This method allows configuration adjustments like secrets and resource caps without modifying the original unit file.

How do I recover a systemd service stuck in a start-limit crash loop?

Recover a systemd service from a start-limit crash loop by managing the service lifecycle and resetting failed states with systemctl. Proper unit hardening and dependency semantics prevent continuous restart failures.

Does managing EOS services with systemd require specific verification steps before deploying?

Managing EOS services with systemd requires deterministic verification workflows using systemctl and systemd-analyze. This validation ensures correct dependency semantics and unit structure before deploying os-* services.