Root launched daemons and distributed objects clash?
Root launched daemons and distributed objects clash?
- Subject: Root launched daemons and distributed objects clash?
- From: Colin Cornaby <email@hidden>
- Date: Fri, 21 Jul 2006 23:33:52 -0700
I have a deamon being launched at startup by launchd, meaning the
daemon is owned by the root user. My user side client attempts to
connect to a distributed object being hosted by the server, which
completes successfully. The client then queries the daemon for it's
status (via the DO) and registers to receive notifications of changes
of the status (again via the DO). The initial status request works
great. The daemon's DO returns the daemon's current status. Things
stop working when the damon attempts to send a message back to the
client that the daemon's status has changed. The message just simply
never goes through. When I run the daemon as the same user as the
client, everything works just fine. Running the daemon as root
prevents the daemon from sending any message back to the client to
tell the client that the daemon's state has changed.
Are there any workarounds to this issue? Do I need to use something
other than DO to make this work? I am running on 10.4.7 Intel.
-Colin
_______________________________________________
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