Re: A CFMessagePort communication disruption can mean only one thing...
Re: A CFMessagePort communication disruption can mean only one thing...
- Subject: Re: A CFMessagePort communication disruption can mean only one thing...
- From: Stéphane Sudre <email@hidden>
- Date: Wed, 12 Nov 2003 17:10:13 +0100
On Wednesday, November 12, 2003, at 04:26 PM, Cameron Hayne wrote:
On 12/11/03 5:29 AM, "Stiphane Sudre" <email@hidden> wrote:
The application is set as a login item (or a startup item if you refer
to the incoherent name in Panther). When the user logs in, it's
launched and is calling:
CFMessagePortRef remote =
CFMessagePortCreateRemote(kCFAllocatorDefault, CFSTR("MY DAEMON"));
on 10.2, remote has never ever been NULL.
on 10.3, remote is sometimes NULL.
What did change in Panther? Is there a workaround for this? Why did it
change?
I read that Panther delays startup of some system services until
needed -
this allows faster booting. Perhaps that is causing your problem? If
so, it
would seem to be a bug that should be reported.
It could have been an explanation but system log is stating the daemon
has been launched at boot time as it should and login occurred later.
_______________________________________________
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.