131
You Don't Love systemd Timers Enough
(blog.tjll.net)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 31 May 2026
131 points (100.0% liked)
Technology
85274 readers
3953 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
I've been doing this stuff for 30 years. The helpful blog post that took 8 pages of text to explain how to schedule a job just made me angry.
I think I am finally into greybeard territory even though my beard made the change a few years ago. Damn.
Why did it make you angry? Do you believe that there are other implementations that do the task better and simpler?
I was mostly kidding. But the little bit that bothered me was the idea that 'it is so simple here are 8 pages to barely scratch the surface.'
cron works fine for me. And if I ever have to work in an environment where I can't use cron and systemd is available, then of course I will use it. Thus far that has never been the case.
Yeah, I think it's just the way the blog post was written. When I was reading it I saw the first few paragraphs was basically "here's how to do Cron with it", and then everything after that was "here's a bunch of other features it has that cron doesn't and how to use those"
I don't think that's the wrong way to write this kind of article, but I could see it feeling overwhelming on a skim, because it may feel like you need to read the whole thing in order to get anything working. But actually only the start was necessary, and the rest was tasty feature pitch.