timers

Manage systemd timer units for scheduled or delayed service activation.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill timers-theslashdojo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: timers
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/systemd/timers
Command: npx skills add https://github.com/theslashdojo/dojo --skill timers-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires systemctl, systemd-analyze, sudo, and includes scripts (resource) components.

What problem does it solve?

Systemd timers replace fragile cron or ad hoc scheduling by providing first-class, managed scheduling for service units, unifying activation, logs, and dependency handling under systemd.

Core Features & Use Cases

  • Calendar and monotonic scheduling: support for calendar expressions and monotonic triggers such as OnBootSec, OnStartupSec, and OnUnitActiveSec for boot-relative or activity-relative jobs.
  • Reliable operations & inspection: validate calendar expressions, install timers into system or user scope, enable/start timers, and report enabled, active, and next-elapse state for programmatic checks.
  • Operational controls: options for persistence to catch up missed runs, randomized delays to avoid thundering herds, accuracy tuning, and optional sudo/scope handling for multi-user deployments.

Quick Start

Use the timers skill to render and install a .timer unit that activates my-service.service daily at 03:00 and then enable and start it.

Frequently Asked Questions about timers

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

FAQPage Schema
How do I schedule recurring jobs with systemd timers as a cron replacement?

Systemd timers replace cron by rendering and installing .timer unit files to activate service units on calendar or monotonic schedules, then enabling and starting them via systemctl for managed, unified job execution. This provides first-class scheduling integrated with systemd logging and dependency handling.

What is the difference between calendar-based and monotonic scheduling in systemd?

Calendar scheduling in systemd uses date and time expressions to trigger units at specific moments, while monotonic scheduling uses relative time events like OnBootSec, OnStartupSec, or OnUnitActiveSec to trigger units after boot or relative to another unit's activation.

How do I validate a systemd calendar expression before enabling a timer?

You can validate a systemd calendar expression using systemd-analyze to parse and confirm the timing logic before installing the .timer file, ensuring the schedule triggers at the expected moments without activation errors.

Can I install systemd timers in user scope without sudo privileges?

Systemd timers can be installed into either system or user scope, with optional sudo handling for system-level deployments. This allows multi-user environments to run scheduled service activations independently without requiring root access for user-level tasks.

How do I prevent thundering herd problems when multiple systemd timers fire simultaneously?

Systemd timers support randomized delays and accuracy tuning to stagger activation times, preventing thundering herd issues when multiple scheduled service units would otherwise trigger at the exact same moment and overwhelm system resources.

Does systemd timer scheduling support catching up missed runs after a reboot?

Systemd timers offer persistence controls to catch up missed runs that would have occurred while the system was offline. This ensures scheduled service activations execute even after downtime, maintaining reliability for critical recurring tasks.