Re: Running processes as non-root after an install
Re: Running processes as non-root after an install
- Subject: Re: Running processes as non-root after an install
- From: Andrew Keller <email@hidden>
- Date: Fri, 09 Nov 2012 18:35:31 -0500
Interesting, I did not think of that approach.
You know, a logout would be less painful than a restart. I expected such a feature to be a different value for the 'postinstall-action' key in the PackageInfo file in a component package, but I was unable to find any documentation to support it.
Can the installer mandate a logout for all users?
Thanks,
Andrew Keller
On Nov 9, 2012, at 3:25 PM, Stephane Sudre wrote:
> /usr/bin/su $USER -c "/usr/bin/open /the/path/to/your/application"
>
> ?
>
> Just out of curiosity, why not just require a logout (since it's an agent)?
>
> On Fri, Nov 9, 2012 at 9:55 AM, Andrew Keller <email@hidden> wrote:
>> Hello all,
>>
>> My installer installs, among other things, a user agent in /Library/LaunchAgents. I understand that it is extremely difficult to start up the user agent because of the multi-user problem, so I am just going to require a restart.
>>
>> Nonetheless, I am curious. Is there an expected way to run commands as the currently logged in user after the install process? I thought about using `sudo -u $USER ...`, but I can think of more than one modification to the sudoers file that would break it.
>>
>> Thanks,
>> Andrew Keller
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden