Hi everyone,
I have an executable that handles NSXPC connectivity between apps that I'm installing, and I would like to install it as a launch daemon. I can do this locally with ease by sudo adding the .plist file to /Library/LaunchDaemons/, but when I tried to do this as part of the installation process, the installer complains about lack of permissions, despite me using su in the post install script:
Is there a best practice when it comes to these services? Currently the plist file and the executable are part of a framework that I am installing.
Thanks!
I have an executable that handles NSXPC connectivity between apps that I'm installing, and I would like to install it as a launch daemon. I can do this locally with ease by sudo adding the .plist file to /Library/LaunchDaemons/, but when I tried to do this as part of the installation process, the installer complains about lack of permissions, despite me using su in the post install script:
Code Block /usr/bin/su - ${loc_user} -c "cp ${plist_path} ${plist_target}" /usr/bin/su - ${loc_user} -c "chown root:wheel ${plist_target}" /usr/bin/su - ${loc_user} -c "chmod 644 ${plist_target}"
Is there a best practice when it comes to these services? Currently the plist file and the executable are part of a framework that I am installing.
Thanks!
The best practice here is to install these files as part of your installer package contents rather than from a post-install script.Is there a best practice when it comes to these services?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"