dezmd@lemmy.world to linuxmemes@lemmy.worldEnglish · edit-22 months agoActual systemd debate (redux)lemmy.worldimagemessage-square8fedilinkarrow-up1152arrow-down114file-text
arrow-up1138arrow-down1imageActual systemd debate (redux)lemmy.worlddezmd@lemmy.world to linuxmemes@lemmy.worldEnglish · edit-22 months agomessage-square8fedilinkfile-text
minus-squareSnot Flickerman@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up13arrow-down1·2 months agocrontab -e 50 8 23 9 * sudo ./systemd-debate.sh
minus-squareExec@pawb.sociallinkfedilinkarrow-up2·2 months agoUnless configured to explicitly blanket allow without authentication I don’t think you can run sudo from cron
minus-squareWolf314159@startrek.websitelinkfedilinkarrow-up5·2 months agoYeah, they got the sudo placement inside out. You “sudo crontab -e” and put your commands there that need sudo, you don’t sudo the individual commands in the regular user’s crontab.
minus-squareleds@feddit.dklinkfedilinkarrow-up2arrow-down1·2 months agoWith systemd this would not be an issue , you just need to set up a timer for your service and some policy rules /s?
minus-squareKusimulkku@lemm.eelinkfedilinkarrow-up2·2 months agoShould’ve used a systemd timer for this
crontab -e 50 8 23 9 * sudo ./systemd-debate.shUnless configured to explicitly blanket allow without authentication I don’t think you can run sudo from cron
Yeah, they got the sudo placement inside out. You “sudo crontab -e” and put your commands there that need sudo, you don’t sudo the individual commands in the regular user’s crontab.
With systemd this would not be an issue , you just need to set up a timer for your service and some policy rules /s?
Should’ve used a systemd timer for this