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 14:04:51 -0800
On Mar 29, 2006, at 1:08 PM, Ethan Funk wrote:
Yes, I did misunderstand you. To answer your question (take 2),
the computer I am doing the development on has no third party AU
components installed.
Gotcha. That still makes me scratch my head because it doesn't sound
like what you are doing is all that different from what coreaudiod
does. My guess is that you still have some linkage, either direct or
indirect, to something that is trying to make a Window Server
connection.
And to follow on with another question: Is there any way,
_any_way_at_all_, to get my daemon to run under a normal user login
session and prevent CoreAudio from muting if/when a fast user
change is performed? If there is, then I will happily run in a
normal login session.
No there isn't, but you can still log in a user through other means
(the login command comes to mind) that don't involve creating a
console session, but do create the bootstrap session and other stuff
you need. My guess is that you would probably need to set up a script
of some sort that got triggered at boot or some other event that
logged in your dummy user and kicked off your daemon. I've never
actually tried doing this, so it might be more involved than that.
Ethan...
On Mar 29, 2006, at 1:50 PM, Jeff Moore wrote:
I think you misunderstand what I was saying. As I understand it,
when you call FindNextComponent (and apparently the other
component look up routines too), the Component Manager has to
build a list of the currently registered components. As such, it
will go through and register in the process all the components,
even ones totally unrelated to what you are doing. Some of these
components require that the Component Manager call the component's
Register method as part of this process. This forces the Component
Manager to load and link the code for at least some of the
components on your system.
What I was proposing was that since I don't see this happening
when coreaudiod launches on my own machine (which has a stock
install of 10.4.5 on it), there may be some other component on
your system that I don't have on mine that is triggering this
message as part of the component registration process. One
possible way this could happen is if you have some AU that doesn't
properly separate it's view components from it's processing
components. Hence my question. What AU's your app is actually
using is beside the point I think.
That said, you mention that you are using QT. I think that this is
the likely culprit as QT links in all sorts of UI related stuff. I
know that the QT folks have done work on their footprint, but I
don't know if they have gotten to the point where they are totally
daemon safe.
One thing you might want to do is to use tools like otool to snoop
through your binary and the binaries it links against to look for
what is loading the code that attempts to make the Window Server
connection.
--
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