merari42@lemmy.world to Programmer Humor@programming.dev · 1 month agoWorks if manually restarted by an intern from time to timelemmy.worldimagemessage-square58linkfedilinkarrow-up1656arrow-down15
arrow-up1651arrow-down1imageWorks if manually restarted by an intern from time to timelemmy.worldmerari42@lemmy.world to Programmer Humor@programming.dev · 1 month agomessage-square58linkfedilink
minus-squarepinball_wizard@lemmy.ziplinkfedilinkarrow-up34·1 month 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-up20·1 month agoAny problem in server administration can be solved with an additional crontab entry. Except for the problem of too many crontab entries.
minus-squareOpisek@piefed.blahaj.zonelinkfedilinkEnglisharrow-up10·1 month 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-squarecurbstickle@anarchist.nexuslinkfedilinkEnglisharrow-up1·1 month agoWhich can be solved by an additional server. Boom, problem solved.
minus-squarekaty ✨@piefed.blahaj.zonelinkfedilinkEnglisharrow-up10·1 month agojust randomly delete 50 of them.
minus-squarepinball_wizard@lemmy.ziplinkfedilinkarrow-up17·1 month 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-up5·1 month agoa crontab can regenerate from bisection to form two whole crontabs
minus-squarerumba@lemmy.ziplinkfedilinkEnglisharrow-up3·1 month agopshaw, just drop in there and combine a few /etc/cron.d/first25 /etc/cron.d/second25 …
minus-squarej_z@feddit.nulinkfedilinkarrow-up2·1 month 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.
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