In general KUNC execute is barely working and just isn't a good
idea. I'm sure we can come up with a better solution if you can
explain the problem you are trying to solve.
Does you driver talk to a dedicated app? Could you write a quick a
dirty unix tool to launch the app in background or monitor the state
of your driver? All sorts of options are available to us that don't
rely on the KUNC.
Godfrey
On 04/28/2005, at 15:15 , Jim Wintermyre wrote:
I'm trying to use KUNCExecute from my IOKit driver in order to
launch a user-space app to do some stuff that can't happen at
kernel level. I'm running into a few snags:
1) It seems that KUNCExceute will only launch an application that
actually lives in the /Applications folder. I'd like to include
the application directly inside the kext bundle, but KUNCExecute
fails to launch the app from there (with no error) even though the
full path is correct. In fact, it doesn't seem to matter where I
put the app, it never gets launched unless it is inside the
/Applications folder. I'm using the full path to specify the app.
Is this how KUNCExecute is supposed to behave? Is this a known limitation?
2) It seems that KUNCExecute will not launch CFM apps. Is this
true? Is there any way around this? I don't think that I can
launch the app via LaunchCFMApp because there doesn't seem to be a
way to pass an argument to the app that KUNCExecute launches.
3) For a test MachO app I created, I get this error from
KUNCExecute when I try to launch using kOpenAppAsRoot:
aped[198]: Attach denied: super-user process, for TestApp[1198]
The same call works fine if I test it on TextEdit. The permissions
on the binary are the same in both cases. Any idea what this means?
