![]() launchd(8) was able to execute the program but the program did return a non-zero exit code. This error code was generated by the program/script. ![]() The error details provided in the tool tip of the job list status column are definitely correct This error code was generated by launchd(8) itself. To find out whether a jobs exit code comes from launchd(8) or the program to be executed watch out for these lines: Click the trace-button in the upper left corner of the log panel and start the job by selecting Job>Start (⌘⇧T) from the menu. Open the log panel by selecting View>Toggle Log (⌘⌥L) from the menu. It is a good idea to have a look at what launchd(8) has to say about the job while trying run it. See bullet "Check the launchd(8) log" to find out if this error reason applies. Move your mouse over the error code to bring up a tool tip with a likely error reason. Hovering over a warning or error sign in a config sections header will provide details about the error/warning.Ĭheck for the exit code of the job in the status column of the job list. Make sure you understand every warning and error that LaunchControl reports. When a change is detected, a request panel will appear: click the Save, Reload and Start button. The preferred method is to start the job unconditionally by selecting Job>Start (⌘⇧T) from the menu. Event triggered jobs might not be executed at all when loading. While debugging a job it is not necessary to load/unload it manually every time a change to the configuration is made.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |