Re: IPC between daemon -> non root app?
Re: IPC between daemon -> non root app?
- Subject: Re: IPC between daemon -> non root app?
- From: Dave Zarzycki <email@hidden>
- Date: Tue, 15 Nov 2005 08:43:50 -0800
That is intentional. What you are running into is how we organize our
Mach bootstrap namespaces.
You need to refactor your code such that communication is _always_
initiated from a client living within a user's login session. A daemon
should never try to initiate communication _to_ a user. A daemon
should only answer requests from processes within sessions.
Be prepared for the fact that:
1) More than one user may be logged in at once.
2) No user may be logged in at all.
3) Don't assume that only one user session is active at a time.
If you have any follow up questions, please don't hesitate to ask them.
davez
On Nov 15, 2005, at 8:29 AM, Philip Lukidis wrote:
Hello, I'm having problems establishing IPC communication between my
test
daemon and a non root app (which for now is a plugin). The means of
communication is CFMessagePort. My app has no problem sending data
to the
daemon, but my daemon cannot open a remote port which the application
created. When I run the daemon under my username (and is thus not
run under
root), the daemon can open the remote port which my app created with
no
problems, and send notifications.
Does anyone have any idea what is behind this? Is it a matter of
permissions? How could this be overcome?
thanks for any ideas,
Philip Lukidis
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden