launchd NFS access
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
FYI, that doesn’t matter in this case because your daemon won’t inherit privileges from launchd.I have launchd and launchctl listed as Full Disk Access.
The name of your daemon.What is DDD?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
So, to be clear, you’re creating an agent not a daemon?I have the *.plist files in ~/Library/LaunchAgents.
Is this part of a product? Or just something that you’re deploying internally?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
I ran into NFS issues from a launchd daemon a few months back. Seems that Catalina forward handles NFS differently. Here's the note I made to myself for future reference. Hopefully it will be of some help. This did solve my issue.
NOTE: Pre-Catalina, a base export path like /Path/to/myFolder works as expected. But in Catalina, the base path to folders now start at /System/Volumes/Data. This is due to major file system changes in Catalina involving APFS, virtual volumes, etc. So now what was /Path/to/myFolder should be exported as /System/Volumes/Data/Path/to/myFolder.
--Barry
Was this ever resolved? I am currently running into the same issue.
No, I haven't solved the issue.