marcos comments on Works if manually restarted by an intern from time to time

[–] marcos@lemmy.world 5 points 1 year ago (5 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...

permalink

fedilink

source

parent

hideshow 5 child comments

[–] dondelelcaro@lemmy.world 9 points 1 year ago (2 children)

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

permalink

fedilink

source

parent

hideshow 2 child comments

[–] marcos@lemmy.world 7 points 1 year ago (1 child)

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

permalink

fedilink

source

parent

hideshow 1 child comment

[–] dondelelcaro@lemmy.world 5 points 1 year ago*

Here you go:

with-lock-ex -q /path/to/lockfile sh -c '
while true; do
    crontab cronfile;
    sleep 60;
done;'

permalink

fedilink

source

parent

[–] bleistift2@sopuli.xyz 8 points 1 year ago* (1 child)

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).

permalink

fedilink

source

parent

hideshow 1 child comment

[–] marcos@lemmy.world 7 points 1 year ago

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

permalink

fedilink

source

parent