[quote='864274022, TyngJJ, /thread/805696?answerId=864274022#864274022, /profile/TyngJJ'] I'm using the terminology from an older document [/quote] Yeah, the terminology here is confusing, which is why I’ve switch to named XPC endpoint. It’s long and clumsy [1], but it’s very clear. Unfortunately there’s no way to get that older doc fixed, because the Documentation Archive is a read-only snapshot. You can’t use the responsible process constraint on a launchd daemon or agent because its named XPC service is published to a Mach bootstrap namespace that allows multiple clients to connect. The first client starts your process and then subsequent clients trigger a new connection to that same process. Given that, the concept of responsible process doesn’t really make sense [2]. What you’re really trying to do here is to ensure that your agent only does work on behalf of your app, and that’s the problem that XPC peer constraints solve. In the case of an launchd agent, it’s best to apply XPC peer constraints
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags: