On Dec 29, 2008, at 6:45 PM, Norman Palardy wrote:
On 29-Dec-08, at 3:58 PM, Arnaud Nicolet wrote:
Le 29 déc. 08 à 23:48 (soir), Norman Palardy a écrit:
Well, as the trash is common for each user, I'd imagine a
GlobalTemporaryItemsFolder would be a good idea.
Trashes are private as well
Things have changed since Mac OS 9...
Ok, I guess there is at least one common folder (the root volume
for instance)...
Trashes are private on all volumes on OS X
Otherwise if I move something to the trash and you go look in the
trash you could read my trash
That would not be secure
Not sure it service apps have any restrictions about starting
other apps (I can't imagine that would be true but it's possible)
Hmm... Perhaps I should make my agent a Console application?
The problem is, in console applications, there is no
DontDaemonize event (and an agent seems to need to be not
daemonized).
Not quite sure I understand why this would make any difference?
Well, I guess console applications and service applications don't
have the same set of API (else they'd not be different, in an RB
point of view).
At least, I have to find a solution...
Service applications are a Windows OS thing more than anything
Not at all; what appears to be the real point of service apps is that
they can be daemonized. This matters on all platforms.
But a console app can be a deamon or not and that can be
controlled via launchd.
It's just an app that is not necessarily owned or controlled by
any user.
So what happen if your daemon is a service application and you
return true in the "DontDaemonize" event (and you tells launchd to
run your app daemonized), or the other way around?
I'd just use a console app on OS X and set things up with launchd
The launchd documentation explicitly tells you not to daemonize
applications.
Charles Yeomans
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|