It's sometimes tricky to get debug logging from launchctl itself, but the keys StandardErrorPath and StandardOutPath can at least help you know if your application is dying due to missing or bad information (an unexpanded environment variable or non-writable path, for example). The key in a file that causes it to start on load is RunAtLoad (and KeepAlive keeps it running if it dies for some reason) RunAtLoad If it's a system-level service (in /Library/LaunchDaemons or /Library/LaunchAgents you may need to do it with sudo (and if you did it without sudo by mistake, you may need to unload it without sudo and then reload it with sudo)
or will not load ever again at login or boot).
The -w means "write" which means that the change will affect reboots (will load every login or boot. Launchctl load -w ~/Library/LaunchAgents/ Generally if you want to "restart" it you unload and reload the config like this: launchctl unload -w ~/Library/LaunchAgents/ stop will stop the service (again, ignoring the schedule).start will start the service (ignoring the schedule, I believe).unload means to stop and unschedule the config file.load means to read the config file and potentially schedule a launch.Launchd can easily get into "weird" states. I created a cross-platform tool to handle creating launchd and systemd service files:
0 kommentar(er)
