launchctl bsexec and El Capitan follow up Q
In order to install some Adobe products when there is no GUI user currently logged in, it has been necessary to use `launchctl bsexec` to run the installation process in the same context as the loginwindow. Adobe documents this technique here: http://www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AAMEE_Ex... <http://www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AAMEE_Exception/en_us/AAMEE_Exceptions_v2_1.pdf> Here is an example from that document: sudo launchctl bsexec `ps auwwx |grep [l]oginwindow | awk '{ print $2 }'` Adobe\ AIR\ Installer.app/Contents/MacOS/Adobe\ AIR\ Installer -silent With the SIP and launchd changes in El Capitan, is there an equivalent? Though I would hope Adobe would fix their installers to not need these silly hacks, even if they do in the future, that’s not going to help the install of current and recent releases. -Greg
One more follow-up question, please. The whole premise of this thread is that the original poster and others need to load launchd jobs into *all* or *other* OS X user accounts. Apps which need to load a job only for the current user account may continue to use "launchctl load” in El Capitan; with no known issues. Is this correct?
participants (2)
-
Gregory Neagle
-
Jerry Krinock