On Mon, Oct 27, 2008 at 5:43 PM, Michael Nickerson <[EMAIL PROTECTED]> wrote:
>
> On Oct 27, 2008, at 12:52 AM, Michael Ash wrote:
>
>> On Mon, Oct 27, 2008 at 12:07 AM, Michael Nickerson
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> You can always set things up to ignore child processes:
>>> signal( SIGCH
On Oct 27, 2008, at 12:52 AM, Michael Ash wrote:
On Mon, Oct 27, 2008 at 12:07 AM, Michael Nickerson
<[EMAIL PROTECTED]> wrote:
You can always set things up to ignore child processes:
signal( SIGCHLD, SIG_IGN );
It's bad to rely on this sort of global state, though. What if some
other bit o
On Mon, Oct 27, 2008 at 12:07 AM, Michael Nickerson
<[EMAIL PROTECTED]> wrote:
>
> On Oct 24, 2008, at 10:46 PM, Michael Ash wrote:
>
>> On Fri, Oct 24, 2008 at 8:46 PM, Tommy Nordgren
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> On 3 okt 2008, at 16.39, Michael Ash wrote:
>>>
...snip
>>>
Nope!
On Oct 24, 2008, at 10:46 PM, Michael Ash wrote:
On Fri, Oct 24, 2008 at 8:46 PM, Tommy Nordgren
<[EMAIL PROTECTED]> wrote:
On 3 okt 2008, at 16.39, Michael Ash wrote:
...snip
Nope! AEWP is a rather broken API in more ways than one. One of the
ways that it's broken is that it is *impossi
On Fri, Oct 24, 2008 at 8:46 PM, Tommy Nordgren
<[EMAIL PROTECTED]> wrote:
>
> On 3 okt 2008, at 16.39, Michael Ash wrote:
>
>> ...snip
>
>> Nope! AEWP is a rather broken API in more ways than one. One of the
>> ways that it's broken is that it is *impossible* to correctly use it
>> without a subpr
On 3 okt 2008, at 16.39, Michael Ash wrote:
...snip
Nope! AEWP is a rather broken API in more ways than one. One of the
ways that it's broken is that it is *impossible* to correctly use it
without a subprocess which will cooperate with you. The reason for
this is that you *must* use wait4 or
On Oct 24, 2008, at 4:52 PM, Dragan Milić wrote:
Assume I created an archiving tool and a user wants to extract some
files from an archive into a directory one hasn't got write
permission for (e.g. /Applictions). Currently, the application shows
alert sheet informing the user of "permissio
Hi all.
Now, I really sincerely apologise for bringing this thread into life
again and for probably abusing the list, since the topic is not
strictly Cocoa, so if moderators mind this, just don't approve the
message. But I need to ask a bit of advice related to privileged
reading/writing
On Fri, Oct 3, 2008 at 12:46 AM, Kelly Graus <[EMAIL PROTECTED]> wrote:
>
> On Oct 2, 2008, at 6:23 PM, Nick Zitzmann wrote:
>
>>
>> On Oct 2, 2008, at 1:30 PM, Kelly Graus wrote:
>>
>>> Is the only way to allow a user to write to a protected location use the
>>> AuthorizationExecuteWithPrivileges
On Oct 2, 2008, at 9:30 PM, Kelly Graus wrote:
Hi Bill,
Thanks for the response!
This is the intended functionality. We are allowing a user to
install system-wide content to our application. We also have the
ability for users to install content for a single user with admin
privileges.
On Oct 2, 2008, at 6:23 PM, Nick Zitzmann wrote:
On Oct 2, 2008, at 1:30 PM, Kelly Graus wrote:
Is the only way to allow a user to write to a protected location
use the AuthorizationExecuteWithPrivileges function?
Yes. AEWP() is most certainly not deprecated.
Ok, I will look into using
Greetings, Kelly!
For this particular purpose, would it be possible to use a package
(.pkg) installer? You can allow the user to choose between
destinations, and such installers handle the authorization for you.
If you intend to allow the content to be installed for the application
from
Hi Bill,
Thanks for the response!
This is the intended functionality. We are allowing a user to install
system-wide content to our application. We also have the ability for
users to install content for a single user with admin privileges.
Kelly
On Oct 2, 2008, at 7:20 PM, Bill Bumgarner
On Oct 2, 2008, at 8:20 PM, Jason Coco wrote:
On Oct 2, 2008, at 21:20 , Bill Bumgarner wrote:
On Oct 2, 2008, at 12:30 PM, Kelly Graus wrote:
Is the only way to allow a user to write to a protected location
use the AuthorizationExecuteWithPrivileges function?
If so, is there a way to tell whe
On Oct 2, 2008, at 21:20 , Bill Bumgarner wrote:
On Oct 2, 2008, at 12:30 PM, Kelly Graus wrote:
Is the only way to allow a user to write to a protected location
use the AuthorizationExecuteWithPrivileges function?
If so, is there a way to tell when the application has quit, and
get the exi
On Oct 2, 2008, at 12:30 PM, Kelly Graus wrote:
Is the only way to allow a user to write to a protected location use
the AuthorizationExecuteWithPrivileges function?
If so, is there a way to tell when the application has quit, and get
the exit code?
If not, how would I go about getting suffici
On Oct 2, 2008, at 1:30 PM, Kelly Graus wrote:
Is the only way to allow a user to write to a protected location use
the AuthorizationExecuteWithPrivileges function?
Yes. AEWP() is most certainly not deprecated.
If so, is there a way to tell when the application has quit, and get
the exit
Hello,
I have an application that needs to be able to write to a protected
directory (either Library/Application Support/ or Applications/
depending on the case). I've separated out all writing operations to
a separate application, which currently is run using NSTask.
I've read the "Perf
18 matches
Mail list logo
