This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
The converter reads a cron line and drafts a timer and a service. It says names, ranges, and day-of-week fields need a review. Persistent runs a missed job after boot, which is a choice. It does not install a unit.
The command in ExecStart is one you already trust. Do not leave the cron line active and also enable the timer. Disable is a later window, after the timer has run once on a lab host. Do not install either during the reading.
One job. The user is named.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.
Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Paste one cron line you administer.
- Read the timer.
- Mark day-of-week and Persistent as reviewed or not.
- Plan to disable the cron line only after the timer works.
- Do not install during the reading.
- Stop.
Mistakes that outlive the command
Crontab to systemd Timer Migration Guide goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Both left enabled.
- A command you do not trust in ExecStart.
- Persistent left on without a decision.
- The units installed during the reading.
- Several jobs in one paste.
Decisions to write down
One decision for Crontab to systemd Timer Migration Guide: One job. The command is one you trust. Persistent is a written choice. Cron will be disabled only after a successful lab run. And nothing was installed.
Checks before you call it done
Confirm this before you call the change done: The schedule is written. The command is written. Persistent is yes or no. Nothing was installed. And both will not stay enabled. If one of those fails, stop.
# One job.
# Review day-of-week.
# Do not enable cron and the timer together.
# Do not install during the reading.Before you leave the host
Crontab to systemd Timer Migration Guide ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.
One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.
A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.