Manifest of Time – Part 3: `systemd-timers` – When the System Breathes on Its Own
"True automation doesn't wait. It lives."
– Philosophy of a breathing system
While `crontab` and `at` need your touch,
`systemd-timers` are like breathing – automatic, deep,
and inseparable from the soul of the system.
This is conscious automation.
Your commands become part of the OS's life rhythm.
What is a `systemd-timer`?
It’s a mechanism where you create two separate units:
- `.service` file – defines WHAT to execute
- `.timer` file – defines WHEN to execute it
They work together – like heart and pulse.
Example: Automatic backup every 6 hours
1. Create the service file
Code:
sudo nano /etc/systemd/system/backup.service
Code:
[Unit]
Description=Backup My Data
[Service]
ExecStart=/usr/local/bin/backup.sh
2. Create the timer file
Code:
sudo nano /etc/systemd/system/backup.timer
Code:
[Unit]
Description=Run backup every 6 hours
[Timer]
OnBootSec=10min
OnUnitActiveSec=6h
Persistent=true
[Install]
WantedBy=timers.target
3. Enable and start the timer
Code:
sudo systemctl daemon-reexec
sudo systemctl enable --now backup.timer
"Your script is now part of the system’s breathing."
Check active timers
Code:
systemctl list-timers
Stop and disable the timer
Code:
sudo systemctl stop backup.timer
sudo systemctl disable backup.timer
Final Thought
With `systemd-timers`,
you don’t just issue commands anymore.
You integrate them into the system’s life cycle.
It doesn’t just run them…
It lives them.
Terminal Signature
Code:
┌──[@iflux@systembreath]
│ trace: [daemon soul linked]
└─> echo "When your code becomes part of the system’s breath… you’ve mastered time."