CFMessagePort : no communication in 10.2 in some cases?
CFMessagePort : no communication in 10.2 in some cases?
- Subject: CFMessagePort : no communication in 10.2 in some cases?
- From: Stéphane Sudre <email@hidden>
- Date: Tue, 17 Sep 2002 13:52:58 +0200
I'm seeing a strange CFMessagePort behavior under 10.2.
A root booted daemon is installing its CFMessagePortRunLoopSource at
boot time and everything is working fine, other applications can send
it CFMessagePort messages.
This daemon is killed with an unfair "kill -9 pid" under root.
The daemon is then launched by root from the command line (i.e.
Terminal.app).
The CFMessagePortRunLoopSource is again created with no problem
(according to the gdb debug session).
When another application tries to communicate with the "daemon", the
CFMessagePortRunLoopSource is not seen:
CFMessagePortRef tDaemonRemote = CFMessagePortCreateRemote(NULL,
CFSTR(MY_DAEMON_MESSAGE_PORT_NAME));
is returning NULL.
Under 10.1, I can kill the Daemon as much as I need, when relaunched,
it's not going to be moody.
I made the test with not loading the daemon at boot time and then just
launched it from the Terminal under root.
Again, it's not possible to communicate with the Daemon,
CFMessagePortCreateRemote returns NULL.
Maybe it's a security feature but I don't see the goal in it.
Currently, I would say it's a bug.
Any other idea?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.