@dezmd to linuxmemesEnglish • edit-22 months agoActual systemd debate (redux)imagemessage-square8arrow-up1155arrow-down115file-text
arrow-up1140arrow-down1imageActual systemd debate (redux)@dezmd to linuxmemesEnglish • edit-22 months agomessage-square8file-text
minus-squareSnot FlickermanlinkfedilinkEnglish13•2 months agocrontab -e 50 8 23 9 * sudo ./systemd-debate.sh
minus-square@[email protected]linkfedilink2•2 months agoUnless configured to explicitly blanket allow without authentication I don’t think you can run sudo from cron
minus-square@[email protected]linkfedilink6•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-square@[email protected]linkfedilink1•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?
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