653
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 01 Oct 2025
653 points (99.2% liked)
Programmer Humor
27758 readers
79 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
Well, here's a sentence I haven't been tempted to use before:
"I believe that may be too many crontab entries."
Any problem in server administration can be solved with an additional crontab entry. Except for the problem of too many crontab entries.
And that's why I added a crontab entry that periodically purges my cron configuration. That way, I'm forced to readd only the truly necessary cron jobs, successfully reducing the amount of crontab entries.
Which can be solved by an additional server.
Boom, problem solved.
just randomly delete 50 of them.
Yes. The strongest crontab entries will probably restore themselves. (For anyone reading along, this is sarcasm. Don't do this.)
a crontab can regenerate from bisection to form two whole crontabs
pshaw, just drop in there and combine a few
/etc/cron.d/first25 /etc/cron.d/second25 ...
This is the way. Exactly what we did + migrated 80% of everything to k8s cronjobs and Argo workflows