Re: Is this program open?
Re: Is this program open?
- Subject: Re: Is this program open?
- From: John Stiles <email@hidden>
- Date: Thu, 13 Apr 2006 14:09:32 -0700
On Apr 13, 2006, at 12:00 PM, Ondra Cada wrote:
John,
On 13.4.2006, at 20:53, John Stiles wrote:
The alternative is the Carbon Process Manager, which I assume
(untested as of yet) does not suffer from this limitation.
Myself I assume it does, for it hardly could not :) Anyway...
There's no way to track that a file has moved? I beg to differ.
Either way, though, it seems like the best approach given the
alternatives, so even if it doesn't work, that's probably how it
will go.
Myself, I would go through ps. It would spare me authentification
and all that stuff, since it's already suid root and It would also
make the complete thing much more secure, for I would not need to
authenticate and root-launch my own stuff, which is always bad and
to be avoided whenever remotely possible.
I hesitate to spawn command-line tasks and parse their output. That
way of coding is a relic from the 80s, IMO.
At any rate, once again—once you get into the realm of links, we
are discussing end-user sabotage, which I don't care about :)
Let's assume, for the purposes of this discussion, that the end
user will not go out of their way to break the process once it
starts to run. If they do, it's really their loss :)
I would not call those things "sabotage" by far. But all right, if
you are about to exclude any "non standard" behaviour, "standard"
being here defined as "non-admin inexperenced user would do this
willingly in Finder", then I guess all right :)
In the case of my app, the user would only have a tiny window of
opportunity to move the files or create links or whatever. It's too
timing-sensitive to happen by accident. _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden