-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
installation location for .plist #50
Labels
Comments
That's a very good question, and definitely worth looking into. Anyone have more experience with |
I use Lingon X (a very nice app for working with Launch Daemons and other automated processes)
When I asked him why Lingon didn’t see Asimov, he replied:
Well probably... I haven’t tried installing it by I can see that there is a launchd job included in it. While it is technically possible to run it from places where Lingon doesn’t see it, it is quite uncommon.
The apple docs say that the launchd startup process reads only from those locations
I don’t restart often but maybe asimov doesn’t restart it’s daily check because of this?
https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html
It loads the parameters for each launch-on-demand user agent from the property list files found in /System/Library/LaunchAgents, /Library/LaunchAgents, and the user’s individual Library/LaunchAgents directory.
btw: thanks for asimov - it saves me tons of space from my years of projects !!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Shouldn't the .plist file be copied to ~/Library/LaunchAgents and then be loaded from there?
I know that it technically works when it's loaded from within the project folder, but doing so goes against the grain -- and may be silently disallowed by Apple at some point in the future.
The text was updated successfully, but these errors were encountered: