this post was submitted on 01 Oct 2025
641 points (99.4% liked)

Programmer Humor

26721 readers
1636 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

founded 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
641
Works if manually restarted by an intern from time to time (lemmy.world)
submitted 3 days ago by merari42@lemmy.world to c/programmer_humor@programming.dev
58 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] marcos@lemmy.world 5 points 3 days ago (2 children)

At some point it may be good to migrate to airflow or something similar.

It's not the number of entries that makes it bad. It's the fact that if you run crontab, they are gone...

[–] dondelelcaro@lemmy.world 10 points 3 days ago (1 children)

That's why there's a crontab rule to load the crontab from a file. Cronception if you will.

[–] marcos@lemmy.world 7 points 3 days ago (1 children)

Make the rule start a secondary cron system. Otherwise it won't run after you erase the crontab.

[–] dondelelcaro@lemmy.world 6 points 3 days ago* (last edited 3 days ago)

Here you go:

with-lock-ex -q /path/to/lockfile sh -c '
while true; do
    crontab cronfile;
    sleep 60;
done;'
[–] bleistift2@sopuli.xyz 8 points 3 days ago* (last edited 3 days ago) (1 children)

At first I thought you missed the -r. Then I checked. Defaulting to STDIN here is very, very dumb, IMHO. Almost as bad as putting the “edit” flag right next to the “delete everything without confirmation” flag on a Western keyboard (-e vs -r).

[–] marcos@lemmy.world 7 points 3 days ago

Crontab is a really badly designed program that we just can't fix because everybody depends on its WFTs for something.