I have a shell script that runs a few (Duplicacy) backup commands. It works fine when I manually run the script from terminal (cd to the directory where it is and then ./backup.sh).
To make it run automatically I created a launch agent (a .plist file). When it runs now, I get only "operation not permitted" errors whenever Duplicacy attempts to open a preference file or any other file to do its backups. The permission of the script is 755, and it's owned by the same user as the the files Duplicacy tried to open.
Quite a bit of research suggests that I should open Security & Privacy in Preferences and allow zsh to have full disk access. I tried this and it solved the problem.
Is this overkill and dangerous for this issue? Is it ok for zsh to have full disk access?
backup.sh
) in a C-script: github.com/restic/restic/issues/2051#issuecomment-560271504 — then you specify the C script binary in the .plist file + allow the binary to have full disk access.