Explanation of launchd: concepts' ambiguity

[scrutinizer11]

Hello,

I read your summary on KeepAlive and RunAtLoad properties and found some grey places that I felt needed clarification. I base my assumptions on an article at https://www.launchd.info and they address what you tried to explain about how the sub-keys "SuccessfulExit" and "NetworkState" affect the parent "KeepAlive" property. You wrote

If an app exits "successfully" (technically, with an exit code = 0) then the app will not be automatically restarted (kept > alive). However, if the app crashes (exit code not equal to 0) then it will be automatically restarted.

As per the explanation in the linked article, "SuccessfulExit" alters the behaviour of the job that's going to be kept alive anyway with the caveat that if the boolean value is TRUE it will be restarted until it fails, and if the boolean is FALSE it will be restarted until it succeeds. So, in both cases, the job will run.
The same is true for "NetworkState": if TRUE then the job will run while or when the connection is up. If FALSE it will run while or when the connection is down.
So your last sentence of those I quoted should've been

If an app exits "successfully" (technically, with an exit code = 0) then the app will be automatically restarted until it fails with non-zero exit code.