Voir https://apple.stackexchange.com/a/102105/1860 pourquoi su
ne fonctionne pas pour toutes les applications.
le bsexec du lancement
Les versions récentes de launchd
ont la possibilité de lancer des applications dans la session d'un autre utilisateur, bien que les ingénieurs d'Apple n'en aient pas recommandé l'usage général.
Utilisez le bsexec
option dans launchctl pour cibler la session utilisateur appropriée :
bslist [PID | ..] [-j]
This prints out Mach bootstrap services and their respective states. While the namespace
appears flat, it is in fact hierarchical, thus allowing for certain services to be only avail-
able to a subset of processes. The three states a service can be in are active ("A"), inactive
("I") and on-demand ("D").
If [PID] is specified, print the Mach bootstrap services available to that PID. If [..] is
specified, print the Mach bootstrap services available in the parent of the current bootstrap.
Note that in Mac OS X v10.6, the per-user Mach bootstrap namespace is flat, so you will only
see a different set of services in a per-user bootstrap if you are in an explicitly-created
bootstrap subset.
If [-j] is specified, each service name will be followed by the name of the job which regis-
tered it.
bsexec PID command [args]
This executes the given command in the same Mach bootstrap namespace hierachy as the given
PID.
bstree [-j]
This prints a hierarchical view of the entire Mach bootstrap tree. If [-j] is specified, each
service name will be followed by the name of the job which registered it. Requires root priv-
ileges.
L'approche recommandée est d'écrire un ticket de travail launchd et de redémarrer le Mac - ou de demander à l'utilisateur de se déconnecter et de se reconnecter.