> On May 25, 2016, at 3:05 PM, Camden Narzt wrote:
>
> I’m sorry, I just assumed anyone doing any dev work on OSX would already run
> homebrew.
I do lots of development work on OS X. I don't run homebrew.
>
> A much smaller test case with no installs so definitely a problem with
> launchd/O
What would happen if there were multiple active users at the same time (like
with Screen Sharing, where the local GUI user and a remote user can both have
active sessions)? Or with a local GUI user and another user SSH’d in?
-Greg
> On Feb 25, 2016, at 5:43 AM, Ludovic Rousseau
> wrote:
>
>
> On Nov 13, 2015, at 4:03 PM, James Bucanek wrote:
>
> Greetings,
>
> I finally had a chance to run this to ground. Here's what I discovered:
>
> Basically, LimitLoadToSessionType=Background is broken. (bug report #23536982)
>
> I was able to narrow down the problem to this simple example. F
> On Nov 5, 2015, at 3:54 PM, James Bucanek wrote:
>
> OK, one last question: Is it ever the case that the home directory/mountpoint
> might disappear *after* a user's Background and Aqua session is created, say
> when they log out?
Sure- a Legacy FileVault home directory would be unmounted,
> On Nov 5, 2015, at 2:23 PM, James Bucanek wrote:
>
> I'm surprised that you say that the home folder might not be available when
> the Background session is created. How is that possible?
Home directories can be mounted at login from a network file share
(AFP/SMB/NFS) or could be encrypted
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/cre
