Re: How is the OS X environment created with Mesos

This probably boils down to not being in the right launchd session. launchd(8) discusses this at a high level. You can see what is going on in your user session with "launchctl print user/$(id -u)". I'm not sure what the right mechanics ought to be for Mesos. It used to be that you would use the

Re: How is the OS X environment created with Mesos

On May 5, 2016, at 13:28, haosdent > wrote: >There is no explicit statement about what Mesos means when it runs a task as >some other user. I think this is just ensure the running user of the task is the user you given. In Mesos, it jus call the

Re: How is the OS X environment created with Mesos

On May 5, 2016, at 13:28, haosdent > wrote: >There is no explicit statement about what Mesos means when it runs a task as >some other user. I think this is just ensure the running user of the task is the user you given. In Mesos, it jus call the

Re: How is the OS X environment created with Mesos

>There is no explicit statement about what Mesos means when it runs a task as some other user. I think this is just ensure the running user of the task is the user you given. In Mesos, it jus call the [setuid](http://linux.die.net/man/2/setuid) to change the user, It would not execute something

How is the OS X environment created with Mesos

Hi, Recently I noticed that the Mesos Jenkins plugin supports the setting of environment variables. Somewhere between 0.26 and 0.28.1, settings like USER= HOME= were required to get things to work the way they had worked. I have been able to set the environment