devops/generator
systemd Timer Generator - Free & Instant | Smocky
Identifies an existing <basename>.service. Letters, digits, underscore, or hyphen, up to 64 characters.
The named service must already exist on the target system. The Execution timeline above shows calendar matches, not guaranteed actual start times or execution history. This Tool never installs or activates the generated Timer.
Frequently asked questions
Does this Tool create or install the systemd service?
No. The generated Timer unit only names a Unit=<basename>.service that must already exist on the target system. This Tool never installs, enables, or activates anything — it only produces the .timer file text.
Why does one Cron expression sometimes produce two OnCalendar lines?
When both the day-of-month and weekday fields are restricted, Cronie combines them with OR, so the generator emits one OnCalendar line per condition — for example "1 * MON" becomes a first-of-month line and a Monday line. A timeline instant matching both still counts once.
Why is Persistent=false in the generated Timer?
Persistent=true would run the service immediately on boot to catch up any occurrence missed while the system was off. This Tool deliberately leaves that choice to you rather than assuming catch-up execution is wanted.