I put cron into the list many months ago when I first ran into this problem. That did seem to help for a while (just checked - it's still in the list).
Jim > On 12/01/2024, at 2:21 PM, Daniel J. Luke <[email protected]> wrote: > > On Dec 1, 2024, at 12:49 PM, Jim Secan <[email protected]> wrote: >> I run scripts via cron which execute MacPorts codes and binaries I build >> using various gcc compilers, several of which access data files on external >> storage. When I rebuild a binary (maybe once every 4-6 months) I often run >> into the problem where macOS refuses to let the binary run because it has >> not been approved for full disk access, which hangs the entire process. >> >> Is there any way, other than manually putting each and every little binary >> into the Full Disk Access list via System Settings, to proactively keep this >> from happening? > > You can add cron to Full Disk Access (that's what I do :) ) > > -- > Daniel J. Luke >
