Timeline for crontab Operation not permitted - cron has full disk access
Current License: CC BY-SA 4.0
15 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 12, 2020 at 16:31 | vote | accept | Michael Yoshpe | ||
Dec 12, 2020 at 16:31 | answer | added | Michael Yoshpe | timeline score: 1 | |
Dec 9, 2020 at 10:33 | comment | added | Scottmeup | It looks like mojave, catalina (and possibly later versions of macOS) treat certain folders such as ~/Desktop as special security cases mjtsai.com/blog/2019/12/18/… | |
Dec 9, 2020 at 8:27 | comment | added | Michael Yoshpe | I tried recreating the file (empty/with content) using vim, and it still has this xattr. However when I create it not on the desktop but in $HOME, this attr does not exist and the cron WORKS. So why would it exist by default in Desktop but no in $HOME? | |
Dec 9, 2020 at 8:10 | comment | added | nohillside♦ |
Hmm, are any ACLs set on that file? Can you remove the file and then just run cat > ~/untitled.sh and type in your script that way (just the shebang and maybe an echo statement)? And then try again with cron?
|
|
Dec 9, 2020 at 7:52 | comment | added | Michael Yoshpe | This file indeed has the extended attr 'com.apple.macl', does this matter? cleaning it with xattr -d doesn't work. @nohillside | |
Dec 8, 2020 at 21:25 | comment | added | nohillside♦ | The @ indicates some extended attributes. Can you check with xattr? | |
Dec 8, 2020 at 12:46 | comment | added | Michael Yoshpe | ls -l output: -rwxr-xr-x@ 1 michael staff 1097 Dec 7 22:30 untitled.sh The contents of the script does not matter, changed it multiple times and it still doesn't run. Also changed it to only include the first row '#!/bin/bash', still no permissions. @Scottmeup | |
Dec 8, 2020 at 11:48 | comment | added | Scottmeup | Does anything interesting come up if you view the long list format of the file details with ls -l? I'd be interested to know what the contents of untitled.sh are, and what the results are from a cron job that points to a script containing only the line: #!/bin/bash | |
Dec 8, 2020 at 6:46 | comment | added | Michael Yoshpe | after adding the corn job and after it runs, I see the error via the mail command. | |
Dec 7, 2020 at 22:21 | comment | added | nohillside♦ | Where/how do you get the error? | |
Dec 7, 2020 at 21:42 | comment | added | Michael Yoshpe | @nohillside yes it does | |
Dec 7, 2020 at 21:18 | comment | added | nohillside♦ | If you run the file in bash, does it work? | |
Dec 7, 2020 at 20:48 | review | First posts | |||
Dec 7, 2020 at 21:18 | |||||
Dec 7, 2020 at 20:44 | history | asked | Michael Yoshpe | CC BY-SA 4.0 |