merari42@lemmy.world to Programmer Humor@programming.dev · 4 days agoWorks if manually restarted by an intern from time to timelemmy.worldimagemessage-square42linkfedilinkarrow-up1644arrow-down14
arrow-up1640arrow-down1imageWorks if manually restarted by an intern from time to timelemmy.worldmerari42@lemmy.world to Programmer Humor@programming.dev · 4 days agomessage-square42linkfedilink
minus-squarepinball_wizard@lemmy.ziplinkfedilinkarrow-up33·4 days agoWell, here’s a sentence I haven’t been tempted to use before: “I believe that may be too many crontab entries.”
minus-squareDickFiasco@sh.itjust.workslinkfedilinkarrow-up18·4 days agoAny problem in server administration can be solved with an additional crontab entry. Except for the problem of too many crontab entries.
minus-squarecurbstickle@anarchist.nexuslinkfedilinkEnglisharrow-up1·1 day agoWhich can be solved by an additional server. Boom, problem solved.
minus-squareOpisek@piefed.blahaj.zonelinkfedilinkEnglisharrow-up8·edit-24 days agoAnd 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.
minus-squarekaty ✨@piefed.blahaj.zonelinkfedilinkEnglisharrow-up9·4 days agojust randomly delete 50 of them.
minus-squarepinball_wizard@lemmy.ziplinkfedilinkarrow-up16·4 days agoYes. The strongest crontab entries will probably restore themselves. (For anyone reading along, this is sarcasm. Don’t do this.)
minus-squarefarngis_mcgiles@sh.itjust.workslinkfedilinkarrow-up4·4 days agoa crontab can regenerate from bisection to form two whole crontabs
minus-squarerumba@lemmy.ziplinkfedilinkEnglisharrow-up3·4 days agopshaw, just drop in there and combine a few /etc/cron.d/first25 /etc/cron.d/second25 …
minus-squarej_z@feddit.nulinkfedilinkarrow-up2·4 days agoThis is the way. Exactly what we did + migrated 80% of everything to k8s cronjobs and Argo workflows
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.
Which can be solved by an additional server.
Boom, problem solved.
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.
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