Re: Another approach to root user?
Re: Another approach to root user?
- Subject: Re: Another approach to root user?
- From: Jeff Moore <email@hidden>
- Date: Wed, 29 Mar 2006 12:07:06 -0800
I was afraid that might happen. At any rate, what I think is going on
is that in the course of initializing itself, the Component Manager
is loading some or all of the system-global components into your
daemon's process. Since these components might be for a variety of
purposes, including UI related operations, one or more of them is
inadvertently attempting to make a connection to the window server.
The question is, why does this happen to your daemon, but not to
coreaudiod, which also loads AU's? I wonder if it's possible that you
have one or more third party AU's (or other components) installed
that are linking their view components in a non-daemon friendly way?
On Mar 29, 2006, at 8:48 AM, Ethan Funk wrote:
OpenADefaultComponent() also fails in the same manner as
FindNextComponent() does. I commented that line of code out, just
to verify, and execution does continue on with out WindowManager
problems. It cant set up and initialize the audiounits of course.
Is this an problem I should take with the component manager people
at Apple?
Ethan...
On Mar 28, 2006, at 7:00 PM, Jeff Moore wrote:
There's no need to call FindNextComponent if you already know the
type and subtype IDs and don't mind getting the "default"
component. If that's the case, you can simply call
OpenADefaultComponent() to get an instance.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden