Expand on emulating cron-like tasks with snooze
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start with the cron page linked in the issue and read the snooze(1) manpage alongside the snooze-hourly, snooze-daily, snooze-weekly and snooze-monthly services. Document concrete runit-native examples for scheduling below hourly granularity and explain how they compare with systemd timers. Done means a newcomer can follow the examples without reverse-engineering the services.
Written by the indexing model from the issue text.
Description
As an alternative to the standard cron implementations, you can use snooze(1) together with the snooze-hourly, snooze-daily, snooze-weekly and snooze-monthly services, which are provided by the snooze package for this purpose. Each of these services execute scripts in the respective /etc/cron.* directories. (ref)
After spending a while scrutinizing the manpage for snooze, I can see that it has a lot of useful functions (timefiles are awesome, rewrote those several times for my cron jobs). But I'm not quite sure how to emulate cron-like behavior with the listed tools, particularly at a granularity less-than hourly. Someone else was recently asking for clarification on snooze services in the IRC as well, which tells me I'm not the only one. (I can kinda get closer by reverse-engineering the snooze-${time}ly services...)
Given that many people who might be reading the cron page in the handbook may be quite new to void & runit services, I think there might be value in adding some croncrete concrete examples/explanation of runit-native scheduling. This might also help people who are trying to figure out the analog for systemd timers.
- Dominant language
- CSS
- Stars
- 217
- Forks
- 212
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from void-linux/void-docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
void-linux/void-docs#849 · 2 comments ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 75/100
void-linux/void-docs#595 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
void-linux/void-docs#532 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
void-linux/void-docs#899 · 5 comments · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
void-linux/void-docs#897 · 5 reactions ·
All issues in void-linux/void-docs
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
priority-0
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100